Triple
T10779051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine expeditionary brigade |
E254268
|
entity |
| Predicate | echelon |
P95417
|
FINISHED |
| Object | mid-sized Marine air-ground task force |
—
|
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: mid-sized Marine air-ground task force | Statement: [Marine expeditionary brigade, echelon, mid-sized Marine air-ground task force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: echelon Context triple: [Marine expeditionary brigade, echelon, mid-sized Marine air-ground task force]
-
A.
eve
Indicates a relationship where one entity is the evening or night-time counterpart, phase, or occurrence associated with another entity.
-
B.
beam
Indicates that one entity emits, directs, or projects a concentrated line or stream (such as light, energy, or information) toward another entity.
-
C.
elite
Indicates that the subject belongs to a select, superior, or highly privileged subset within a larger group or category.
-
D.
elevation
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
-
E.
eon
Indicates a very long, often immeasurable or indefinitely extended, span of time between entities or events.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732c25478819093dedec0c8556777 |
completed | April 9, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69d6f31455648190b5c24690487b1b54 |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa334b8c819082eaf8537084c323 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:16 p.m.