Triple
T30367570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neal Dunn |
E772460
|
entity |
| Predicate | service number or rank |
P143165
|
FINISHED |
| Object | Major |
—
|
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: Major | Statement: [Neal Dunn, service number or rank, Major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: service number or rank Context triple: [Neal Dunn, service number or rank, Major]
-
A.
serviceNumberOrRank
chosen
Indicates that one entity is identified by, or associated with, the service number or rank of another entity.
-
B.
serviceNumberOrYearsOfService
Indicates a relationship that specifies either an entity’s service identification number or the duration of time the entity has served.
-
C.
militaryServiceNumber
Indicates the unique identification number assigned to an individual for tracking their record in a military service context.
-
D.
militaryRank
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
-
E.
civilServiceRank
Indicates that one entity holds a specific rank or position within a civil service hierarchy relative to another entity or classification.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 29, 2026, 7:58 p.m.