Triple
T32794447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Place Jules-Ferry |
E838718
|
entity |
| Predicate | hasPostalAddressInMunicipality |
P21214
|
FINISHED |
| Object | Paris |
—
|
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: Paris | Statement: [Place Jules-Ferry, hasPostalAddressInMunicipality, Paris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPostalAddressInMunicipality Context triple: [Place Jules-Ferry, hasPostalAddressInMunicipality, Paris]
-
A.
hasPostalAddressComponent
Indicates that an entity is associated with a specific part or element of a postal address (such as street, city, or postal code).
-
B.
hasNameInMunicipality
Indicates that an entity is known by a particular name within the context or jurisdiction of a specific municipality.
-
C.
isInMunicipality
chosen
Indicates that one entity (typically a place or address) is located within the administrative boundaries of a specific municipality.
-
D.
hasPostalServiceCity
Indicates that a location is served by or associated with a particular city’s postal service.
-
E.
hasPostalRole
Indicates that an entity holds or is assigned a specific role or function within a postal or mail-related context.
- 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_69f3493c7f6881908edf2aa13631d1e0 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fec5c503808190bde0b1829ea43071 |
completed | May 9, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69fec535dd6c8190a6ab85201f5a04a9 |
completed | May 9, 2026, 5:25 a.m. |
Created at: May 1, 2026, 1:14 a.m.