Triple
T15713981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General (United States Army) |
E380911
|
entity |
| Predicate | isSeniorMostRegularRank |
P59713
|
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: [General (United States Army), isSeniorMostRegularRank, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSeniorMostRegularRank Context triple: [General (United States Army), isSeniorMostRegularRank, true]
-
A.
seniorRank
Indicates that one entity holds a higher or more senior rank or position than another entity.
-
B.
isHighestCeremonialRankIn
Indicates that an entity holds the top ceremonial position or title within a specified group, organization, or jurisdiction.
-
C.
isSeniorTitle
chosen
Indicates that one title holds a higher or more senior rank or status relative to another title.
-
D.
hasSeniorNCO
Indicates that an entity has, is assigned, or is associated with a senior non-commissioned officer in a supervisory or leadership capacity.
-
E.
isHighestRankedUniformedOfficerIn
Indicates that one entity holds the top-ranking position among all uniformed officers within a specified organization or 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04f90aea0819082a9e9fe0f7780b0 |
completed | April 16, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:45 a.m.