Triple
T32159142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French Legation (Austin) |
E821377
|
entity |
| Predicate | inUseAsLegationFrom |
P173649
|
FINISHED |
| Object | 1841 |
—
|
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: 1841 | Statement: [French Legation (Austin), inUseAsLegationFrom, 1841]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUseAsLegationFrom Context triple: [French Legation (Austin), inUseAsLegationFrom, 1841]
-
A.
ledLegationTo
Indicates that one entity headed or directed a diplomatic mission or delegation to another entity or location.
-
B.
usedDiplomaticMission
Indicates that one entity employed or relied on a particular diplomatic mission as a means or channel to carry out some action or achieve some objective.
-
C.
hasDiplomaticStaffFrom
Indicates that an entity has diplomatic personnel who originate from or represent another specified entity.
-
D.
hasDiplomaticMission
Indicates that one entity maintains an official diplomatic representation, such as an embassy or mission, in the territory or jurisdiction of another entity.
-
E.
hasConsulateOfUnitedStatesIn
Indicates that a consulate of the United States is located in the specified place.
- 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_69f34905e098819082191a6922a6d607 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba19733881909567a0c5af4b9966 |
completed | May 3, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:32 a.m.