Triple
T38532813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Starshina |
E923411
|
entity |
| Predicate | roughEquivalentRank |
P19071
|
FINISHED |
| Object | master sergeant |
—
|
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: master sergeant | Statement: [Starshina, roughEquivalentRank, master sergeant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roughEquivalentRank Context triple: [Starshina, roughEquivalentRank, master sergeant]
-
A.
rankEquivalent
chosen
Indicates that two entities hold the same rank or hierarchical level within a given ordering or classification system.
-
B.
rankGrade
Indicates the grade or level assigned to an entity within a ranking or evaluation system.
-
C.
hasApproximateRanking
Indicates that one entity is assigned a non-exact, estimated, or relative position or order with respect to others.
-
D.
depthRank
Indicates the relative ordering of entities based on how deep or distant they are along a specified depth dimension or hierarchy.
-
E.
representsRank
Indicates that one entity serves as the rank, status, or hierarchical level assigned to another entity.
- 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_69f76ea8f6348190a5c03fb6292bbee3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:32 p.m.