Triple
T22077899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicole |
E545568
|
entity |
| Predicate | relationshipToMaster |
P146559
|
FINISHED |
| Object | Servant to Monsieur Jourdain |
—
|
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: Servant to Monsieur Jourdain | Statement: [Nicole, relationshipToMaster, Servant to Monsieur Jourdain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToMaster Context triple: [Nicole, relationshipToMaster, Servant to Monsieur Jourdain]
-
A.
relationshipToBond
Indicates the specific type of personal, familial, or professional relationship an entity has to the person named Bond.
-
B.
relationshipManaged
Indicates that one entity oversees, directs, or maintains responsibility for the ongoing management of a relationship involving another entity.
-
C.
identityRelation
Indicates that two entities are in fact the very same entity, not merely similar or equivalent.
-
D.
relationshipToMother
Indicates the specific familial or social connection an entity has to its mother.
-
E.
referralRelationship
Indicates a relationship in which one entity directs or recommends another entity to a third party for services, information, or further action.
- 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_69e11e3523488190badd54b5d580c00d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128b38844819084526372fa6c6e35 |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
| PDg | Predicate description generation | batch_69e6fad59ef48190b62a2af636918a15 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:28 p.m.