Triple
T37627324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | staff sergeant |
E936245
|
entity |
| Predicate | hasTypicalCommand |
P86670
|
FINISHED |
| Object | squad |
—
|
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: squad | Statement: [staff sergeant, hasTypicalCommand, squad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalCommand Context triple: [staff sergeant, hasTypicalCommand, squad]
-
A.
hasCommand
Indicates that one entity possesses, controls, or is associated with a specific command or directive applied to another entity or process.
-
B.
containsCommand
Indicates that one entity includes or embeds a command directed at or executable by another entity.
-
C.
typicalCommands
chosen
Indicates that the associated entity commonly issues or uses the specified commands as part of its normal or expected behavior.
-
D.
hasCommandSystem
Indicates that one entity possesses, uses, or is associated with a particular command or control system.
-
E.
hasCommandStructure
Indicates that one entity possesses an organized hierarchy of authority or control that governs another entity or set of entities.
- 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_69f76ed24820819081bafd36e9088701 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffecdcbac4819093b725a7dbe0e61b |
completed | May 10, 2026, 2:26 a.m. |
| PD | Predicate disambiguation | batch_69ffec3633288190adbbd84e277708dc |
completed | May 10, 2026, 2:23 a.m. |
Created at: May 3, 2026, 4:18 p.m.