Triple
T900991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Lieutenant |
E19444
|
entity |
| Predicate | isEquivalentToRank |
P19071
|
FINISHED |
| Object | Ensign |
—
|
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: Ensign | Statement: [Second Lieutenant, isEquivalentToRank, Ensign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEquivalentToRank Context triple: [Second Lieutenant, isEquivalentToRank, Ensign]
-
A.
hasComparableRank
Indicates that two entities hold positions or levels that are equivalent or similar in rank within a given hierarchy or system.
-
B.
rankEquivalent
chosen
Indicates that two entities hold the same rank or hierarchical level within a given ordering or classification system.
-
C.
isRankedAbove
Indicates that one entity holds a higher position or status in an ordered ranking than another entity.
-
D.
usesRankStructureSimilarTo
Indicates that one entity organizes or orders its elements according to a ranking system that is similar to the ranking system used by another entity.
-
E.
hasRankOrder
Indicates that one entity is ordered or positioned relative to others according to a specific ranking or sequence.
- 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad42ecac81909f8bc554d2fe0363 |
completed | March 1, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69a4aa979d408190b17ccfde132ea628 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.