Triple
T14493502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lt |
E359425
|
entity |
| Predicate | isCommissionedRankAbbreviation |
P114446
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Lt, isCommissionedRankAbbreviation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommissionedRankAbbreviation Context triple: [Lt, isCommissionedRankAbbreviation, yes]
-
A.
commissionedOfficerRank
Indicates that one entity holds a rank that qualifies them as a commissioned officer in a formal organizational hierarchy.
-
B.
isMilitaryRank
Indicates that one entity holds a specific position or level within a formal military hierarchy in relation to another.
-
C.
isMilitaryOrderGrade
Indicates that one entity is classified as a specific grade or level within a military order or honor system in relation to another entity.
-
D.
equivalentRankInNOAACommissionedOfficerCorps
Indicates that two positions or grades hold the same rank level within the NOAA Commissioned Officer Corps.
-
E.
namedForMilitaryRank
Indicates that one entity is named after or in honor of a specific military rank held by a person or associated with a military position.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de930f34d08190b4b30e54e2f702ed |
completed | April 14, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69de5c4ccba08190a988bfda0bc9f5cb |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:21 a.m.