Triple
T26397320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General (United Kingdom) |
E663601
|
entity |
| Predicate | higherRankStatus |
P39281
|
FINISHED |
| Object | wartime or honorary rank |
—
|
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: wartime or honorary rank | Statement: [General (United Kingdom), higherRankStatus, wartime or honorary rank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: higherRankStatus Context triple: [General (United Kingdom), higherRankStatus, wartime or honorary rank]
-
A.
higherRankHas
Indicates that one entity holds a higher rank or hierarchical position than another entity.
-
B.
higherRankDescription
chosen
Indicates that one entity holds a superior or more senior rank or status compared to another entity.
-
C.
rankStatus
Indicates the hierarchical level or position an entity holds within an ordered ranking or status system.
-
D.
rankingStatus
Indicates the relative position or level an entity holds within an ordered ranking or hierarchy.
-
E.
upperLevelStatus
Indicates that one entity holds a higher-level, superior, or overarching status relative to another within a hierarchy or layered structure.
- 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 26, 2026, 11:29 p.m.