Triple
T754764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brigade 2506 |
E15528
|
entity |
| Predicate | capturedMembers |
P19121
|
FINISHED |
| Object | over 1100 |
—
|
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: over 1100 | Statement: [Brigade 2506, capturedMembers, over 1100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capturedMembers Context triple: [Brigade 2506, capturedMembers, over 1100]
-
A.
hasMembers
Indicates that a group, organization, or collection includes certain entities as its members.
-
B.
eligibleMembers
Indicates that certain entities meet the required criteria or conditions to be considered eligible members of a specified group or category.
-
C.
typicalMembers
Indicates that the related entities are representative or characteristic members of a larger group, category, or class.
-
D.
primaryMembers
Indicates that the related entities are the main or most important members within a larger group or organization.
-
E.
capturedBy
Indicates that one entity has been seized, taken into control, or otherwise apprehended by another entity.
- 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_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a66820548190b373deb117187c2c |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a501c4cc81908de6d63e3d4f60d7 |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a5bed20c81909ecc28bf42594e72 |
completed | March 1, 2026, 8:46 p.m. |
Created at: March 1, 2026, 7:37 p.m.