Triple
T11152029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosie Cotton |
E263808
|
entity |
| Predicate | marriedInYear |
P98119
|
FINISHED |
| Object | 3020 Third Age |
—
|
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: 3020 Third Age | Statement: [Rosie Cotton, marriedInYear, 3020 Third Age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriedInYear Context triple: [Rosie Cotton, marriedInYear, 3020 Third Age]
-
A.
marriedOn
Indicates that a marriage event took place on a specific date for the related entities.
-
B.
marriedIn
Indicates that two entities entered into a marital relationship at a specific place or within a particular jurisdiction.
-
C.
marriedBy
Indicates that one entity is the officiant or authority who performs and formalizes the marriage of another entity.
-
D.
spouseOfSince
Indicates that two individuals are spouses and specifies the date or time from which their marital relationship has been in effect.
-
E.
marriageDate
Indicates the specific date on which two entities entered into a marital relationship.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8719e74819095413abc6c79296c |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75ce71944819089eee9b5c9283cbd |
completed | April 9, 2026, 8:01 a.m. |
| PDg | Predicate description generation | batch_69d7706116248190a87440bec3960884 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:28 p.m.