Triple
T8572063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elizabeth Tilley |
E202948
|
entity |
| Predicate | spouseMarriageDate |
P67588
|
FINISHED |
| Object | about 1623 |
—
|
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: about 1623 | Statement: [Elizabeth Tilley, spouseMarriageDate, about 1623]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseMarriageDate Context triple: [Elizabeth Tilley, spouseMarriageDate, about 1623]
-
A.
marriageDate
Indicates the specific date on which two entities entered into a marital relationship.
-
B.
spouseOfSince
chosen
Indicates that two individuals are spouses and specifies the date or time from which their marital relationship has been in effect.
-
C.
metSpouseAt
Indicates that one person first encountered or became acquainted with their spouse at a particular place, event, or time.
-
D.
spouseNameAtMarriage
Indicates the full name a person’s spouse had at the time of their marriage.
-
E.
marriedBy
Indicates that one entity is the officiant or authority who performs and formalizes the marriage of another entity.
- 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_69ca8327b0a881908606ff860713964d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbea43843c8190ac2224d427bb7a75 |
completed | March 31, 2026, 3:37 p.m. |
| PD | Predicate disambiguation | batch_69cbd11856048190a1ce4b83a38f6965 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:21 p.m.