Triple
T27291069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rue Plumet |
E688626
|
entity |
| Predicate | relatedWorkLocation |
P199697
|
FINISHED |
| Object | Rue de la Chanvrerie |
—
|
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: Rue de la Chanvrerie | Statement: [Rue Plumet, relatedWorkLocation, Rue de la Chanvrerie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedWorkLocation Context triple: [Rue Plumet, relatedWorkLocation, Rue de la Chanvrerie]
-
A.
locationInWork
Indicates that one entity specifies the place or setting where another entity occurs, is situated, or takes place within a particular work (e.g., a scene’s location in a film or a chapter’s setting in a book).
-
B.
locationOfWork
Indicates the place or site where an entity performs its work or carries out its professional activities.
-
C.
workedInLocation
Indicates that an entity performed work or held a job in a specified geographic location or place.
-
D.
worksNear
Indicates that one entity performs its work or duties in close physical proximity to another entity.
-
E.
hasWorksLocatedIn
Indicates that the works or creations associated with an entity are situated or stored in a specified location.
- 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_69ef355a96308190a2bed991525fb278 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69ff519b65f081909902ba83b775ef85 |
completed | May 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69ff506fccdc8190bd93269589040aed |
completed | May 9, 2026, 3:19 p.m. |
| PDg | Predicate description generation | batch_69ff519a67008190b1eda931fdeff53e |
completed | May 9, 2026, 3:24 p.m. |
Created at: April 27, 2026, 11:15 a.m.