Triple
T31004097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Cup match vs Red Star Belgrade |
E790017
|
entity |
| Predicate | leg |
P40286
|
FINISHED |
| Object | second leg |
—
|
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: second leg | Statement: [European Cup match vs Red Star Belgrade, leg, second leg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leg Context triple: [European Cup match vs Red Star Belgrade, leg, second leg]
-
A.
legs
Indicates that an entity possesses legs, specifying the presence or number of leg-like appendages associated with it.
-
B.
thighsGiveRiseTo
Indicates that one entity’s thighs generate, produce, or give origin to another entity or feature.
-
C.
legCharacteristic
Indicates a characteristic, property, or attribute that specifically pertains to the legs of an entity.
-
D.
triadLeg
Indicates that an entity functions as one of the three supporting legs or components in a triadic structure or system.
-
E.
firstLeg
chosen
Indicates that one entity represents the initial segment or starting portion of a multi-part journey, sequence, or process involving another entity.
- 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:57 p.m.