Triple
T27700125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Land Shark Stadium |
E698403
|
entity |
| Predicate | alsoKnownAsDuringPeriod |
P39
|
FINISHED |
| Object | LandShark Stadium |
—
|
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: LandShark Stadium | Statement: [Land Shark Stadium, alsoKnownAsDuringPeriod, LandShark Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoKnownAsDuringPeriod Context triple: [Land Shark Stadium, alsoKnownAsDuringPeriod, LandShark Stadium]
-
A.
officialNameDuringPeriod
Indicates that an entity had a specific official name that was valid only during a particular time period.
-
B.
laterBecameKnownAs
Indicates that an entity was previously known by one name or identity and, at a later time, came to be known by a different name or identity.
-
C.
alsoKnownAs
chosen
Indicates that one entity is an alternative name, alias, or designation for another entity.
-
D.
previousNamePeriod
Indicates the time span during which an entity was known by a former name before changing to its current name.
-
E.
formerNamePeriodStart
Indicates the date or time point when an entity began using a former name that is being recorded.
- 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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f635a29ff08190bfd246ccaf0ddb4e |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:56 p.m.