Triple
T37476701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reharmont |
E931298
|
entity |
| Predicate | postalServicesProvidedFrom |
P90695
|
FINISHED |
| Object | Trois-Ponts |
—
|
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: Trois-Ponts | Statement: [Reharmont, postalServicesProvidedFrom, Trois-Ponts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postalServicesProvidedFrom Context triple: [Reharmont, postalServicesProvidedFrom, Trois-Ponts]
-
A.
postalService
Indicates a relationship where one entity provides or manages the delivery and handling of mail and packages for another entity.
-
B.
hasPostalServiceThrough
chosen
Indicates that one entity receives or provides postal services by means of, or via the infrastructure of, another entity.
-
C.
postalServiceDesignation
Indicates the official classification or label assigned to an entity by a postal service for mail handling, routing, or addressing purposes.
-
D.
governingPostalOperator
Indicates that one postal operator has official authority or regulatory control over the operations of another postal service or postal area.
-
E.
hasPostalAgency
Indicates that one entity operates, hosts, or is served by a postal agency associated with another entity.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8e6631588190a1a9ce9289f4ccb0 |
completed | May 6, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0c53c08190b64291bac58cdb4c |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.