Triple
T8717492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O-10 |
E206931
|
entity |
| Predicate | typicalRankTitleInArmy |
P52914
|
FINISHED |
| Object | General |
—
|
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: General | Statement: [O-10, typicalRankTitleInArmy, General]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRankTitleInArmy Context triple: [O-10, typicalRankTitleInArmy, General]
-
A.
militaryRank
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
-
B.
isMilitaryRank
chosen
Indicates that one entity holds a specific position or level within a formal military hierarchy in relation to another.
-
C.
militaryRankScope
Indicates the hierarchical level or range of authority that a military rank applies to within an organizational or operational context.
-
D.
usesMilitaryRanks
Indicates that a system, organization, or context employs formal military rank titles to define roles, hierarchy, or status among its members.
-
E.
regimentalTitle
Indicates the formal or official title assigned to a military regiment within an organizational or historical context.
- 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5cdac6988190b9f9cc1f350aae53 |
completed | March 31, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69cc456e806c819087e7d66ee737f242 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:36 p.m.