Triple
T35790481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoenix Lights |
E1034679
|
entity |
| Predicate | notableCityWitnessed |
P206048
|
FINISHED |
| Object | Phoenix |
E133906
|
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: Phoenix | Statement: [Phoenix Lights, notableCityWitnessed, Phoenix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCityWitnessed Context triple: [Phoenix Lights, notableCityWitnessed, Phoenix]
-
A.
notableInCity
Indicates that an entity is particularly prominent, recognized, or significant within a specific city.
-
B.
notableCityIncluded
Indicates that a notable or significant city is contained within, or is part of, a larger geographic or administrative entity.
-
C.
notableCityOfOperation
Indicates that a city is a primary or particularly significant location where an entity conducts its operations or activities.
-
D.
historicalEventWitnessed
Indicates that an entity personally observed or was present at a particular historical event.
-
E.
notableEventMentionedIn
Indicates that a particular notable event is referenced or discussed within a specified source or document.
- F. None of above. chosen
Provenance (5 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_69f76e1575908190aaa306d843b41c14 |
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_6a38cb7b215c8190b14bae56d4e47cb4 |
completed | June 22, 2026, 5:43 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037ce53de881908cf14141cf3bc570 |
completed | May 12, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:06 p.m.