Triple
T27801012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jackson Town Square |
E702239
|
entity |
| Predicate | hasCornerStructure |
P199574
|
FINISHED |
| Object | northwest elk antler arch |
—
|
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: northwest elk antler arch | Statement: [Jackson Town Square, hasCornerStructure, northwest elk antler arch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCornerStructure Context triple: [Jackson Town Square, hasCornerStructure, northwest elk antler arch]
-
A.
hasCorner
Indicates that one entity possesses or includes a corner that is part of or associated with another entity.
-
B.
hasCornerCount
Indicates that an entity is associated with a specific number of corners.
-
C.
hasTypeOfCorner
Indicates that one entity possesses or is characterized by a specific kind or category of corner.
-
D.
haveStructure
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
-
E.
hasSlowCorners
Indicates that an entity possesses corners or turning points that are navigated or traversed at a relatively low speed.
- F. None of above. chosen
Provenance (4 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69ff46afe7e481908f2862ed11c88db2 |
completed | May 9, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69ff45e9151881909c444a655e852165 |
completed | May 9, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69ff46aefe248190a80d898df6ef1340 |
completed | May 9, 2026, 2:37 p.m. |
Created at: April 27, 2026, 5:34 p.m.