Triple
T30176349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atticus James Hallisay |
E767068
|
entity |
| Predicate | parentMarriageStatus |
P81808
|
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: [Atticus James Hallisay, parentMarriageStatus, married]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentMarriageStatus Context triple: [Atticus James Hallisay, parentMarriageStatus, married]
-
A.
parentsMarriageStatus
chosen
Indicates the marital status relationship between an individual’s parents (e.g., married, divorced, separated, never married).
-
B.
parentsMarriedAt
Indicates that the parents of the given entity were married at the specified time or date.
-
C.
marital status
Indicates the legal or social state of a person’s marriage-related relationship, such as being single, married, divorced, or widowed.
-
D.
spouseStatusAtMarriage
Indicates the marital status each partner held at the time their marriage to one another was formed.
-
E.
spouseStatus
Indicates the marital relationship status between two individuals, such as whether they are currently spouses, formerly spouses, or not married to each other.
- 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_69f2247ba20c81909d34f2bfed706e1e |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 29, 2026, 7:25 p.m.