Triple
T1929564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SLT |
E40911
|
entity |
| Predicate | typicalEquipmentLevel |
P33559
|
FINISHED |
| Object | well-equipped |
—
|
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: well-equipped | Statement: [SLT, typicalEquipmentLevel, well-equipped]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEquipmentLevel Context triple: [SLT, typicalEquipmentLevel, well-equipped]
-
A.
typicalCommandLevel
Indicates the usual or standard level of authority or access at which a command is intended to be executed.
-
B.
teamLevel
Indicates the hierarchical rank or tier at which a team operates within an organization, competition, or structure.
-
C.
trainingLevel
Indicates the degree or stage of training or skill development that an entity has attained.
-
D.
typicalGradeLevel
Indicates the usual or most common educational grade level at which something (such as a concept, resource, or skill) is intended to be taught or is typically encountered.
-
E.
hasTypicalArmor
Indicates that an entity normally wears or is equipped with a standard or characteristic type of armor.
- 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_69a8864711648190b07bed24ed76258e |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb266dcb4819090be83556615d0db |
completed | March 7, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_69abafeec6f881909d47acb966683279 |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb20c4970819086e66a5435744297 |
completed | March 7, 2026, 5:05 a.m. |
Created at: March 4, 2026, 7:35 p.m.