Triple
T21083917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Embassy in Tehran |
E519438
|
entity |
| Predicate | notableBuildingOnSite |
P57645
|
FINISHED |
| Object | chancery building |
—
|
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: chancery building | Statement: [U.S. Embassy in Tehran, notableBuildingOnSite, chancery building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBuildingOnSite Context triple: [U.S. Embassy in Tehran, notableBuildingOnSite, chancery building]
-
A.
notableBuildingAssociated
chosen
Indicates a relationship where a notable or significant building is associated with, connected to, or relevant to a given entity.
-
B.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
C.
notableSiteAssociatedWith
Indicates that there is a significant or noteworthy site or location that is associated with, related to, or prominently linked to the given entity.
-
D.
emblematicBuildingLocation
Indicates that a building serves as a symbolic or representative landmark for a particular location or area.
-
E.
notableSiteListedOn
Indicates that a notable site is recorded or referenced within a particular list, registry, or catalog.
- 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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e70948704481908b8b75a2ecc42bb6 |
completed | April 21, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:49 p.m.