Triple
T26023195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lisbon Lions Stand |
E647210
|
entity |
| Predicate | associatedCityOfVictory |
P29757
|
FINISHED |
| Object | Lisbon |
—
|
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: Lisbon | Statement: [Lisbon Lions Stand, associatedCityOfVictory, Lisbon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCityOfVictory Context triple: [Lisbon Lions Stand, associatedCityOfVictory, Lisbon]
-
A.
conqueredCity
Indicates that one entity has taken control of a city from another entity, typically through military force or domination.
-
B.
victoryLocation
chosen
Indicates the place or setting where a victory or triumph occurs.
-
C.
enemyCity
Indicates a relationship where one city is considered an adversary or opponent of another city, typically in a conflict or hostile context.
-
D.
wasCitadelOf
Indicates that a place previously served as the main fortified stronghold or central defensive structure for another entity.
-
E.
cityOfChampion
Indicates that a particular city is recognized as the home or representative city of a given champion or championship-winning 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_69e77e8aa65881909ca58918f29ab2a0 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
Created at: April 22, 2026, 9:04 a.m.