Triple
T35680982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teğmen |
E1031007
|
entity |
| Predicate | commandLevelTypical |
P11280
|
FINISHED |
| Object | platoon |
—
|
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: platoon | Statement: [Teğmen, commandLevelTypical, platoon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandLevelTypical Context triple: [Teğmen, commandLevelTypical, platoon]
-
A.
typicalCommandLevel
chosen
Indicates the usual or standard level of authority or access at which a command is intended to be executed.
-
B.
commandLevel
Indicates the hierarchical degree of authority or control one entity holds over another within a command structure.
-
C.
typicalCommandRank
Indicates the usual or most common rank at which an individual typically holds command authority in a given context.
-
D.
typicalHighestLevel
Indicates the usual or most common maximum level or degree that something typically reaches within a given context.
-
E.
typicalCommands
Indicates that the associated entity commonly issues or uses the specified commands as part of its normal or expected behavior.
- 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_69f76e0bb6608190ad3a1880be54a17d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: May 3, 2026, 4:05 p.m.