Triple
T2649625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 22nd Marine Expeditionary Unit |
E53864
|
entity |
| Predicate | taskOrganization |
P14302
|
FINISHED |
| Object | scalable |
—
|
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: scalable | Statement: [22nd Marine Expeditionary Unit, taskOrganization, scalable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taskOrganization Context triple: [22nd Marine Expeditionary Unit, taskOrganization, scalable]
-
A.
organizedAs
Indicates how elements are structured, arranged, or grouped according to a particular organizing principle or scheme.
-
B.
taskForce
chosen
Indicates a collaborative relationship in which multiple entities are formally grouped to work together as a specialized team on a specific task or mission.
-
C.
organizedUnder
Indicates that one entity is administratively or structurally placed within, and governed or managed by, another entity.
-
D.
organizedDuring
Indicates that an event or activity was arranged or took place within a specified time period or temporal context.
-
E.
agendaItem
Indicates that something is an item or entry on a planned agenda or schedule of topics to be addressed.
- 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_69ab495e192081909c77b622e8e7e15a |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd91ca1288190ba302b04bac4c153 |
completed | March 7, 2026, 7:51 a.m. |
| PD | Predicate disambiguation | batch_69abd814298c8190952f05aed43f6bb8 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.