Triple
T16354573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Combat Training Battalion |
E397141
|
entity |
| Predicate | followsTrainingPhase |
P75500
|
FINISHED |
| Object | recruit training |
—
|
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: recruit training | Statement: [Marine Combat Training Battalion, followsTrainingPhase, recruit training]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsTrainingPhase Context triple: [Marine Combat Training Battalion, followsTrainingPhase, recruit training]
-
A.
includesTrainingPhase
Indicates that something contains or encompasses a specific training phase as part of its overall process or structure.
-
B.
followOnPhases
chosen
Indicates that certain phases occur subsequently as a continuation or next steps after preceding phases.
-
C.
usesTrainingStrategy
Indicates that one entity applies or follows a particular training strategy in carrying out its learning or optimization process.
-
D.
hasTrainingFor
Indicates that an entity has received or possesses training that prepares it for performing a specific task, role, or function.
-
E.
laterTrainingGroup
Indicates that one training group occurs chronologically after another training group.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2facd80dc8190b08f0eecbf787240 |
completed | April 18, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.