Triple
T31991304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maison Louis Carré |
E816875
|
entity |
| Predicate | hasClientOccupation |
P191905
|
FINISHED |
| Object | art dealer |
—
|
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: art dealer | Statement: [Maison Louis Carré, hasClientOccupation, art dealer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClientOccupation Context triple: [Maison Louis Carré, hasClientOccupation, art dealer]
-
A.
hasOccupancy
Indicates that an entity is currently filled, used, or inhabited to a certain extent or by a certain number of occupants.
-
B.
hasModelOccupation
Indicates that an entity’s occupation or job role is that of a model.
-
C.
hasRelativeOccupation
Indicates that two people are related in such a way that one’s occupation is defined or characterized in relation to the other’s occupation.
-
D.
hasOccupationOfResident
Indicates that one entity holds the role or status of being a resident in relation to another entity or context.
-
E.
holderIsOccupation
Indicates that the holder entity has the specified occupation or job role.
- 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_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69fcef636dfc819085cf91323f2e4edd |
completed | May 7, 2026, 8 p.m. |
Created at: May 1, 2026, 12:13 a.m.