Triple
T35805413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batista vs Triple H |
E1035089
|
entity |
| Predicate | firstMajorMatchCity |
P90028
|
FINISHED |
| Object | Los Angeles, California |
E158960
|
NE 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: Los Angeles, California | Statement: [Batista vs Triple H, firstMajorMatchCity, Los Angeles, California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMajorMatchCity Context triple: [Batista vs Triple H, firstMajorMatchCity, Los Angeles, California]
-
A.
thirdMajorMatchCity
Indicates that the city associated with the third major entity in a sequence matches a specified city.
-
B.
firstMajorRunCity
chosen
Indicates the city where an entity’s first major run, performance, or large-scale event initially took place.
-
C.
finalMatchCity
Indicates the city where the final match of a competition or tournament takes place.
-
D.
firstMatchCity
Indicates that the referenced city is the first one that matches a given set of criteria or search conditions among multiple possible cities.
-
E.
homeCityForMajorStadium
Indicates that a city serves as the home location for a particular major stadium.
- F. None of above.
Provenance (4 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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a389bffe5d081909f4917c712268c2c |
completed | June 22, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.