Triple
T25723112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | commodore (historical U.S. Navy rank) |
E645042
|
entity |
| Predicate | abolishedAsPermanentRank |
P50768
|
FINISHED |
| Object | 1899 |
—
|
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: 1899 | Statement: [commodore (historical U.S. Navy rank), abolishedAsPermanentRank, 1899]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abolishedAsPermanentRank Context triple: [commodore (historical U.S. Navy rank), abolishedAsPermanentRank, 1899]
-
A.
wasStrippedOfRank
Indicates that an entity had its rank or status removed, typically as a form of punishment or disciplinary action.
-
B.
rankAbolished
chosen
Indicates that a particular rank, title, or position has been officially discontinued or removed from use.
-
C.
abolishedAfter
Indicates that one entity was abolished at a later time than another entity was abolished.
-
D.
abolishedDuring
Indicates that an entity or practice ceased to exist or was officially ended within the time period defined by another entity.
-
E.
abolishedAsSystem
Indicates that something (typically an institution, practice, or system) has been officially ended and no longer exists as an organized or recognized system.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fc683cd48190bf4bab9cb8de691a |
completed | May 2, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69f480824a1c81908a8a492eedbc2596 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 10:05 p.m.