Triple
T34002913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fifth Avenue mansion at 1048 Fifth Avenue |
E871873
|
entity |
| Predicate | hasCornerLocation |
P26784
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Fifth Avenue mansion at 1048 Fifth Avenue, hasCornerLocation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCornerLocation Context triple: [Fifth Avenue mansion at 1048 Fifth Avenue, hasCornerLocation, true]
-
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.
hasCornerStructure
Indicates that one entity possesses or includes a structural element specifically located at or forming a corner of something.
-
D.
locatedAtCornerOf
chosen
Indicates that one entity is positioned at or forms the corner where two or more boundaries, edges, or intersecting paths meet.
-
E.
hasTypeOfCorner
Indicates that one entity possesses or is characterized by a specific kind or category of corner.
- 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_69f3499f8cbc81908de6ec89fa91ea8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:50 a.m.