Triple
T16108704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glena Goranson |
E390810
|
entity |
| Predicate | marriedToSinceCollege |
P67588
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Glena Goranson, marriedToSinceCollege, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriedToSinceCollege Context triple: [Glena Goranson, marriedToSinceCollege, true]
-
A.
marriedInYear
Indicates that two entities are married to each other in a specific calendar year.
-
B.
marriedOn
Indicates that a marriage event took place on a specific date for the related entities.
-
C.
spouseOfSince
chosen
Indicates that two individuals are spouses and specifies the date or time from which their marital relationship has been in effect.
-
D.
marriedBy
Indicates that one entity is the officiant or authority who performs and formalizes the marriage of another entity.
-
E.
marriedIn
Indicates that two entities entered into a marital relationship at a specific place or within a particular jurisdiction.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e20165aa9c81908c5358cca2b0d0fe |
completed | April 17, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.