Triple
T3506447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Training School 103 |
E74085
|
entity |
| Predicate | missionTypePrepared |
P42909
|
FINISHED |
| Object | behind-the-lines operations |
—
|
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: behind-the-lines operations | Statement: [Special Training School 103, missionTypePrepared, behind-the-lines operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionTypePrepared Context triple: [Special Training School 103, missionTypePrepared, behind-the-lines operations]
-
A.
missionPlanning
Indicates the process of defining, organizing, and coordinating actions or operations needed to achieve a specific mission objective.
-
B.
intendedMission
chosen
Indicates that one entity is the planned or designated mission, task, or objective associated with another entity.
-
C.
missionName
Indicates the designated title or label assigned to a specific mission or operation.
-
D.
missionStart
Indicates the point in time or event at which a mission or task officially begins.
-
E.
commanderPlanned
Indicates that a commander formulated or devised a plan for a particular action, operation, or objective.
- 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbf52bd8819085a2ac5f48cc5c68 |
completed | March 8, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69adae0e770481908528fa35eda53003 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.