Triple
T37123424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 46th Infantry Regiment |
E919324
|
entity |
| Predicate | hasMultipleFormations |
P197686
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [46th Infantry Regiment, hasMultipleFormations, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultipleFormations Context triple: [46th Infantry Regiment, hasMultipleFormations, true]
-
A.
hasFiveMajorFormations
Indicates that an entity possesses or is associated with exactly five primary or principal formations.
-
B.
possibleFormation
Indicates that one entity is capable of being formed, created, or produced from another entity or set of entities under certain conditions.
-
C.
numberOfFormations
Indicates the count of distinct formations associated with or involved in a given entity or context.
-
D.
hasMultipleArrangements
Indicates that an entity can exist or be configured in more than one distinct arrangement or setup.
-
E.
containsFormation
Indicates that one entity spatially or structurally includes or encloses a formation as part of its extent or composition.
- 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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
| PDg | Predicate description generation | batch_69fea1f4daa88190bd3cc1ace684e77f |
completed | May 9, 2026, 2:54 a.m. |
Created at: May 3, 2026, 4:15 p.m.