Triple
T11848912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | motor rifle division |
E281855
|
entity |
| Predicate | successorFormations |
P14054
|
FINISHED |
| Object | motor rifle brigades |
—
|
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: motor rifle brigades | Statement: [motor rifle division, successorFormations, motor rifle brigades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorFormations Context triple: [motor rifle division, successorFormations, motor rifle brigades]
-
A.
successorForce
Indicates that one force or power succeeds, replaces, or takes over the role of another force.
-
B.
successorGroups
Indicates that one group is the direct successor or follow-up group to another group in some sequence or lineage.
-
C.
successorCollection
Indicates that one collection directly follows or comes after another collection in an ordered sequence.
-
D.
successorDivision
chosen
Indicates that one division is the organizational successor that continues or replaces the role, functions, or identity of another division.
-
E.
successorFoundedBy
Indicates that an entity was founded by the successor of another specified 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a65c72088190b8de9550c455b788 |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a254a57481908a1e6ad97919c416 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.