Triple
T19681512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Empire |
E472601
|
entity |
| Predicate | hasHomeEvent |
P132813
|
FINISHED |
| Object | New York leg of the Global Champions League |
—
|
LITERAL FINISHED |
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: New York leg of the Global Champions League | Statement: [New York Empire, hasHomeEvent, New York leg of the Global Champions League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeEvent Context triple: [New York Empire, hasHomeEvent, New York leg of the Global Champions League]
-
A.
hasHomeStatusInEvent
chosen
Indicates that an entity holds the home (host) status or role within the context of a specific event.
-
B.
hasPublicEventsIn
Indicates that an entity organizes or holds public events within a specified location or context.
-
C.
hasHome
Indicates that an entity possesses or is associated with a place where it lives or is based.
-
D.
hasOccasionalEvent
Indicates that an event or activity occurs irregularly or infrequently in relation to a given entity or context.
-
E.
hasHomeProgram
Indicates that an entity is associated with or belongs to a primary or designated home program.
- 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e641bf97348190bc31b00ed4ec6cad |
completed | April 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:45 p.m.