Triple
T33596721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur Clutterbuck |
E860586
|
entity |
| Predicate | parentMarriage |
P148171
|
FINISHED |
| Object | parents married in 2006 |
—
|
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: parents married in 2006 | Statement: [Arthur Clutterbuck, parentMarriage, parents married in 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentMarriage Context triple: [Arthur Clutterbuck, parentMarriage, parents married in 2006]
-
A.
parentsMarriedAt
chosen
Indicates that the parents of the given entity were married at the specified time or date.
-
B.
parentsMarriageStatus
Indicates the marital status relationship between an individual’s parents (e.g., married, divorced, separated, never married).
-
C.
maritalRelations
Indicates a legally or socially recognized spousal relationship or marriage-based connection between two entities.
-
D.
connectedThroughMarriageVia
Indicates that two entities are related to each other by a marital connection that is mediated through one or more intermediate spouses or in-laws, rather than by a direct marriage between them.
-
E.
spouseParentage
Indicates that one entity is a parent of the other entity’s spouse.
- 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_69f3497f35908190a2e9bbb9b96c7a3f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: May 1, 2026, 1:41 a.m.