Triple
T32775160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kershaw’s Brigade marker |
E838178
|
entity |
| Predicate | honorsUnitType |
P179269
|
FINISHED |
| Object | brigade |
—
|
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: brigade | Statement: [Kershaw’s Brigade marker, honorsUnitType, brigade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorsUnitType Context triple: [Kershaw’s Brigade marker, honorsUnitType, brigade]
-
A.
honourType
Indicates the specific category or classification of an honour or award associated with an entity.
-
B.
unitOfRecognition
Indicates that one entity serves as the formal unit, level, or granularity at which another entity is identified, measured, or acknowledged.
-
C.
oversawUnitType
Indicates that an entity had supervisory or managerial responsibility over a particular type or category of unit.
-
D.
notableUnitType
Indicates that an entity is notably associated with, characterized by, or best known for a particular type of unit (such as an organizational, measurement, or structural unit).
-
E.
typeOfUnitCommanded
Indicates the specific type or category of military or organizational unit that an entity is in command of.
- 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_69f3493a824c8190938489ba69041d08 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7201e241c819092d56a7bb99dc94d |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: May 1, 2026, 1:13 a.m.