Triple
T31991305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maison Louis Carré |
E816875
|
entity |
| Predicate | hasOriginalClient |
P194865
|
FINISHED |
| Object | Louis Carré |
—
|
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: Louis Carré | Statement: [Maison Louis Carré, hasOriginalClient, Louis Carré]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalClient Context triple: [Maison Louis Carré, hasOriginalClient, Louis Carré]
-
A.
hasOriginalVersion
Indicates that one entity is the original or initial version from which another entity is derived or adapted.
-
B.
hasOriginalBearer
Indicates that something was initially possessed, held, or borne by a particular entity before any transfer, change, or reassignment occurred.
-
C.
hasOriginalPart
Indicates that an entity includes a component or segment that is part of its initial, original composition.
-
D.
hasOriginalTerminal
Indicates that an entity is associated with or derived from a specific original terminal element in a structure or system.
-
E.
hasOriginalLocation
Indicates that an entity was initially located or situated at a specified place or position before any change or movement occurred.
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
| PDg | Predicate description generation | batch_69fd8ccaee848190acd59d7d643ad062 |
completed | May 8, 2026, 7:12 a.m. |
Created at: May 1, 2026, 12:13 a.m.