Triple
T14281812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capitão-tenente |
E354066
|
entity |
| Predicate | equivalentRankInPortugueseArmy |
P113585
|
FINISHED |
| Object | capitão |
—
|
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: capitão | Statement: [Capitão-tenente, equivalentRankInPortugueseArmy, capitão]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equivalentRankInPortugueseArmy Context triple: [Capitão-tenente, equivalentRankInPortugueseArmy, capitão]
-
A.
equivalentRankInBritishArmy
Indicates that two military positions are considered to have the same rank level within the structure of the British Army.
-
B.
correspondingRankInUSArmy
Indicates that one military rank is the equivalent or closest matching rank within the hierarchy of the United States Army.
-
C.
equivalentAirForceRank
Indicates that two military positions or titles correspond to the same rank level within different air forces.
-
D.
militaryRank
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
-
E.
equivalentRankInNOAACommissionedOfficerCorps
Indicates that two positions or grades hold the same rank level within the NOAA Commissioned Officer Corps.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de697b5e8081908e5b91a3a1c55df9 |
completed | April 14, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a88446481909cd526da97a3b70f |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:10 a.m.