Triple
T31601742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Motors pavilion |
E806364
|
entity |
| Predicate | sponsorReplacedBy |
P96865
|
FINISHED |
| Object | Chevrolet |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Chevrolet | Statement: [General Motors pavilion, sponsorReplacedBy, Chevrolet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsorReplacedBy Context triple: [General Motors pavilion, sponsorReplacedBy, Chevrolet]
-
A.
sponsorTo
Indicates that one entity provides support, funding, or endorsement to another entity, typically to enable or promote the latter’s activities or initiatives.
-
B.
sponsorshipChangeTo
chosen
Indicates a change in sponsorship where an entity becomes the new sponsor of another entity, replacing or updating the previous sponsorship arrangement.
-
C.
sponsorFrom
Indicates that one entity provides sponsorship or financial backing originating from a specified source entity.
-
D.
sponsorshipRenamedFrom
Indicates that a sponsorship currently known by one name previously existed under a different, earlier name.
-
E.
sponsorEnded
Indicates that a sponsorship relationship between entities has been terminated or has come to an end.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 10:33 p.m.