Triple
T31428495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman military institutions |
E801729
|
entity |
| Predicate | hasTrainingPractice |
P88361
|
FINISHED |
| Object | standardized drill |
—
|
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: standardized drill | Statement: [Roman military institutions, hasTrainingPractice, standardized drill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrainingPractice Context triple: [Roman military institutions, hasTrainingPractice, standardized drill]
-
A.
hasTrainingFor
Indicates that an entity has received or possesses training that prepares it for performing a specific task, role, or function.
-
B.
hasPractices
chosen
Indicates that an entity engages in, follows, or carries out specific practices, methods, or customary ways of doing things.
-
C.
hasTrainingTrack
Indicates that an entity is associated with or assigned to a specific training track or program.
-
D.
hasTrainingComplex
Indicates that an entity possesses or is associated with a dedicated facility or complex used for training activities.
-
E.
hasPracticum
Indicates that an entity includes, requires, or is associated with a practical training or hands-on learning component.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fec5c503808190bde0b1829ea43071 |
completed | May 9, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69fec535dd6c8190a6ab85201f5a04a9 |
completed | May 9, 2026, 5:25 a.m. |
Created at: April 30, 2026, 8:55 p.m.