Triple
T36938734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lorraine Blake |
E913688
|
entity |
| Predicate | hasSpouseRank |
P138446
|
FINISHED |
| Object | Lieutenant Colonel |
—
|
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: Lieutenant Colonel | Statement: [Lorraine Blake, hasSpouseRank, Lieutenant Colonel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpouseRank Context triple: [Lorraine Blake, hasSpouseRank, Lieutenant Colonel]
-
A.
marriedToRank
Indicates that one entity is married to another entity who holds a specific rank or position.
-
B.
hasSpouseMilitaryRank
chosen
Indicates that a person’s spouse holds a specific military rank.
-
C.
hasSpousePositionInFamily
Indicates that a person’s spouse holds a specific role or position within the family structure.
-
D.
hasSpouseInLineage
Indicates that one entity has, within its ancestral or descendant line, another entity who is or was their spouse.
-
E.
hasSpouseTitle
Indicates that a person’s spouse holds a particular title or honorific designation.
- 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_69f76e8a6a5c81909c1febf32bf3fe23 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
Created at: May 3, 2026, 4:13 p.m.