Triple
T33461453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louise McIntyre |
E856925
|
entity |
| Predicate | hasSpouseMilitaryBranch |
P135286
|
FINISHED |
| Object | U.S. Army |
—
|
NE NERFINISHED |
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: U.S. Army | Statement: [Louise McIntyre, hasSpouseMilitaryBranch, U.S. Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpouseMilitaryBranch Context triple: [Louise McIntyre, hasSpouseMilitaryBranch, U.S. Army]
-
A.
spouseServiceBranch
chosen
Indicates the military or service branch in which a person’s spouse serves or has served.
-
B.
hasSpouseMilitaryRank
Indicates that a person’s spouse holds a specific military rank.
-
C.
militarySpouseOf
Indicates that one person is or was the legally recognized spouse of another person who is serving or has served in the military.
-
D.
spouseOfMilitaryUnit
Indicates that one entity is the spouse or marital partner of a member associated with the specified military unit.
-
E.
spouseCountryOfService
Indicates the country where a person’s spouse is or was serving in an official or professional capacity.
- 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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: May 1, 2026, 1:37 a.m.