Triple
T30134457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southard Street |
E765948
|
entity |
| Predicate | adjacentToAttraction |
P3449
|
FINISHED |
| Object | Truman Annex |
—
|
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: Truman Annex | Statement: [Southard Street, adjacentToAttraction, Truman Annex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjacentToAttraction Context triple: [Southard Street, adjacentToAttraction, Truman Annex]
-
A.
attractionBasedOn
Indicates a relationship where one entity is drawn to or interested in another specifically because of certain attributes, qualities, or characteristics that the latter possesses.
-
B.
hasSimilarAttraction
Indicates that two entities experience or exert a comparable level or type of attraction toward something or each other.
-
C.
isAdjacentTo
Indicates that one entity is directly next to or bordering another without anything of the same type in between.
-
D.
hasAttractionNearby
chosen
Indicates that one entity is located close to another entity that serves as an attraction or point of interest.
-
E.
relatedAttraction
Indicates that one attraction is associated with or connected to another attraction in some relevant way.
- 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_69f22477d1a081908df2b7e6ed16859d |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 29, 2026, 7:16 p.m.