Triple
T2251700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catherine Vance Freeman |
E49630
|
entity |
| Predicate | spouseMilitaryRank |
P4765
|
FINISHED |
| Object | Fleet Admiral |
—
|
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: Fleet Admiral | Statement: [Catherine Vance Freeman, spouseMilitaryRank, Fleet Admiral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseMilitaryRank Context triple: [Catherine Vance Freeman, spouseMilitaryRank, Fleet Admiral]
-
A.
spouseOffice
Indicates that one entity holds an office or position that is associated with, or held by, the spouse of another entity.
-
B.
spouseOccupation
chosen
Indicates that one person’s spouse has a particular job, profession, or occupation.
-
C.
militaryRank
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
-
D.
spouseStatus
Indicates the marital relationship status between two individuals, such as whether they are currently spouses, formerly spouses, or not married to each other.
-
E.
spouseMemberOf
Indicates that a person’s spouse is a member of a specified group, organization, or 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_69a88aaa9250819095e127d0d77e8a32 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc11d04688190abc04fac3a1804a9 |
completed | March 7, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69abbdb34c148190b51e99f540f97204 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.