Triple
T38284386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Plaza (Hub) |
E1022163
|
entity |
| Predicate | radiatesTo |
P72721
|
FINISHED |
| Object | Main Street, U.S.A. |
—
|
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: Main Street, U.S.A. | Statement: [Central Plaza (Hub), radiatesTo, Main Street, U.S.A.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radiatesTo Context triple: [Central Plaza (Hub), radiatesTo, Main Street, U.S.A.]
-
A.
radiatedFrom
Indicates that something (such as energy, particles, or influence) originates at a source and spreads outward from that source.
-
B.
radiantIn
Indicates that one entity emits or shines light, energy, or brilliance within or into another entity or space.
-
C.
isRadialRouteOf
chosen
Indicates that one route functions as a radial connection extending outward from a central point, hub, or main route.
-
D.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
E.
radiant
Indicates that one entity emits or gives off light, energy, or brilliance toward or around another.
- 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_69f76df0cddc81908d16c1556ff4097f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.