Triple
T5918301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Tanz |
E131635
|
entity |
| Predicate | isMilitaryOfficer |
P67691
|
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 Tanz, isMilitaryOfficer, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMilitaryOfficer Context triple: [General Tanz, isMilitaryOfficer, true]
-
A.
isMilitaryRank
Indicates that one entity holds a specific position or level within a formal military hierarchy in relation to another.
-
B.
hasMilitaryAuthority
Indicates that one entity possesses formal power or command to direct, control, or make decisions over the military activities or forces of another entity.
-
C.
hasMilitaryStatus
Indicates that an entity possesses a specific military affiliation, role, or status (such as active duty, reserve, or veteran).
-
D.
isMilitaryOrderGrade
Indicates that one entity is classified as a specific grade or level within a military order or honor system in relation to another entity.
-
E.
isMilitaryPostType
Indicates that something is classified as a type or category of military post or installation.
- F. None of above. chosen
Provenance (4 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_69c0085a1ed08190a7e9a8b6323fd680 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c048fc112c8190b905bf561c9de096 |
completed | March 22, 2026, 7:54 p.m. |
| PD | Predicate disambiguation | batch_69c03352208c8190968efed05a9fd416 |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c048fb02a081908e78629e1e283cd0 |
completed | March 22, 2026, 7:54 p.m. |
Created at: March 22, 2026, 3:59 p.m.