Triple
T1038934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fleet Master Chief Petty Officer |
E22425
|
entity |
| Predicate | typicalBilletLevel |
P11280
|
FINISHED |
| Object | fleet-level command |
—
|
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: fleet-level command | Statement: [Fleet Master Chief Petty Officer, typicalBilletLevel, fleet-level command]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBilletLevel Context triple: [Fleet Master Chief Petty Officer, typicalBilletLevel, fleet-level command]
-
A.
typicalCommandLevel
chosen
Indicates the usual or standard level of authority or access at which a command is intended to be executed.
-
B.
typicalDegree
Indicates the usual or characteristic level, intensity, or extent to which something holds or applies in a given context.
-
C.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
D.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
E.
typicallyHoldsRank
Indicates that an entity is most commonly or usually associated with holding a particular rank or level in a hierarchy.
- 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_69a493d91478819094cc01fb65564bc1 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b97c64a88190bf1119fdd4940bf3 |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b729f8488190b2042bd9c625a833 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.