Triple
T14670335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monsieur Josserand |
E344492
|
entity |
| Predicate | buildingOfResidence |
P75
|
FINISHED |
| Object | apartment house on Rue de Choiseul |
—
|
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: apartment house on Rue de Choiseul | Statement: [Monsieur Josserand, buildingOfResidence, apartment house on Rue de Choiseul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingOfResidence Context triple: [Monsieur Josserand, buildingOfResidence, apartment house on Rue de Choiseul]
-
A.
residence
chosen
Indicates that one entity lives at, is based in, or habitually occupies the location represented by the other entity.
-
B.
residenceType
Indicates the kind or category of dwelling or living arrangement associated with an entity.
-
C.
ownedResidence
Indicates that one entity has ownership of a dwelling or place of residence associated with another entity.
-
D.
houseLocatedIn
Indicates that a house is situated within or belongs to a specific geographic location or area.
-
E.
architectOfResidence
Indicates that one entity is the architect responsible for designing the residence 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb54ef2908190b189ced65eec434a |
completed | April 14, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.