Triple
T21622183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tweeter Center |
E533603
|
entity |
| Predicate | operatedAsNameDuring |
P21988
|
FINISHED |
| Object | late 1990s |
—
|
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: late 1990s | Statement: [Tweeter Center, operatedAsNameDuring, late 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedAsNameDuring Context triple: [Tweeter Center, operatedAsNameDuring, late 1990s]
-
A.
operatedAsNameUntil
Indicates that an entity functioned or was known under a particular name up to a specified point in time.
-
B.
laterOperatedUnder
Indicates that an entity, after an earlier period, was subsequently managed, controlled, or conducted under a different name, organization, framework, or operational context.
-
C.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
-
D.
officialNameDuringPeriod
chosen
Indicates that an entity had a specific official name that was valid only during a particular time period.
-
E.
heldAtFormerName
Indicates that an event or activity took place at a location when it was known by a previous or former name.
- 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef3bb0c42c8190997fbeb7a764d60e |
completed | April 27, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:34 p.m.