Triple
T30864894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hôtel de Langeac site |
E786170
|
entity |
| Predicate | streetAddressNow |
P170808
|
FINISHED |
| Object | near Place des États-Unis, Paris |
—
|
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: near Place des États-Unis, Paris | Statement: [Hôtel de Langeac site, streetAddressNow, near Place des États-Unis, Paris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetAddressNow Context triple: [Hôtel de Langeac site, streetAddressNow, near Place des États-Unis, Paris]
-
A.
streetAddress
Indicates the specific location of an entity in terms of its numbered building and street name within a postal address.
-
B.
locationAddressed
Indicates that a communication, message, or action is specifically directed to or intended for a particular location or address.
-
C.
address
Indicates that one entity directs spoken or written communication specifically to another entity.
-
D.
addressRepresents
Indicates that one address stands for, corresponds to, or serves as the official representation of another entity or location.
-
E.
addressLocal
Indicates that one entity serves as a local or nearby address or location reference for another entity.
- 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 29, 2026, 8:47 p.m.