Triple
T33931034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 144th Armored Signal Company |
E869889
|
entity |
| Predicate | supportedFormationRole |
P86919
|
FINISHED |
| Object | armored warfare |
—
|
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: armored warfare | Statement: [144th Armored Signal Company, supportedFormationRole, armored warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedFormationRole Context triple: [144th Armored Signal Company, supportedFormationRole, armored warfare]
-
A.
supportedFormation
Indicates that one entity provided assistance, resources, or conditions that enabled the creation or establishment of another entity or structure.
-
B.
supportedFormationType
chosen
Indicates the type of formation that an entity is capable of supporting or is designed to work with.
-
C.
hasRoleInFormationOf
Indicates that an entity plays a specific role or function in the creation, development, or establishment of another entity or structure.
-
D.
supportsRole
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to perform or occupy a specific role.
-
E.
preferredFormation
Indicates that one entity is the favored or most commonly used arrangement, configuration, or setup associated with another entity.
- 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_69f3499a59788190bff762a891471b31 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:49 a.m.