Triple
T34330853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Motte family (fictional) |
E881001
|
entity |
| Predicate | marriedCouple |
P193958
|
FINISHED |
| Object | Monsieur La Motte and Madame La Motte |
—
|
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: Monsieur La Motte and Madame La Motte | Statement: [La Motte family (fictional), marriedCouple, Monsieur La Motte and Madame La Motte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriedCouple Context triple: [La Motte family (fictional), marriedCouple, Monsieur La Motte and Madame La Motte]
-
A.
marriedIn
Indicates that two entities entered into a marital relationship at a specific place or within a particular jurisdiction.
-
B.
marriedBy
Indicates that one entity is the officiant or authority who performs and formalizes the marriage of another entity.
-
C.
marriedInto
Indicates that one entity became connected to another’s family or group through marriage, rather than by birth or prior membership.
-
D.
marriedAfter
Indicates that one marriage occurred later in time than another specified marriage.
-
E.
laterMarriedIn
Indicates that two entities became married at a later time relative to a previously referenced event or marital status.
- 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_69f349ba96a08190b94887bae2d8ee49 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
| PDg | Predicate description generation | batch_69fd5bf49288819098a12202411cba4f |
completed | May 8, 2026, 3:43 a.m. |
Created at: May 1, 2026, 1:58 a.m.