Triple
T30390524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miles Tuck |
E773067
|
entity |
| Predicate | hasMaritalStatusBeforeImmortality |
P199646
|
FINISHED |
| Object | married |
—
|
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: married | Statement: [Miles Tuck, hasMaritalStatusBeforeImmortality, married]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaritalStatusBeforeImmortality Context triple: [Miles Tuck, hasMaritalStatusBeforeImmortality, married]
-
A.
statusBeforeMarriage
chosen
Indicates the civil, social, or legal status an individual held prior to entering into a marriage.
-
B.
hasMaritalStatusAtEnd
Indicates that an entity possesses a specific marital status at the end of a given period, event, or reference time.
-
C.
hasMaritalStatusAfterFirstMarriage
Indicates that an entity’s marital status at a given time is the one it holds after its first marriage has occurred.
-
D.
maritalStatusBeforeRenunciation
Indicates the marital status a person had prior to formally renouncing a role, status, or affiliation.
-
E.
characterMaritalHistory
Indicates a relationship that records the sequence of a character’s past and present marital relationships, including spouses and relevant time periods.
- 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_69f2248ef0a48190aa54d4d8ac3e5758 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff9d9cb4f8819083682be3c483b599 |
completed | May 9, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69ff9c38bf9c8190bbb85b32f3ae3d2e |
completed | May 9, 2026, 8:42 p.m. |
Created at: April 29, 2026, 8:02 p.m.