Triple
T27853801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batalla de Las Piedras |
E704029
|
entity |
| Predicate | bando2 |
P70728
|
FINISHED |
| Object | tropas realistas españolas |
—
|
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: tropas realistas españolas | Statement: [Batalla de Las Piedras, bando2, tropas realistas españolas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bando2 Context triple: [Batalla de Las Piedras, bando2, tropas realistas españolas]
-
A.
bando
Indicates a relationship where an entity is placed under a ban, prohibition, or outlaw status imposed by some authority.
-
B.
bando1
Indicates a relationship where an entity is associated with or belongs to a specific group, faction, or band.
-
C.
B_2
chosen
Indicates a secondary or alternative type of binary relationship between two entities, often used as a variant or refinement of a primary relation B.
-
D.
secondaryBand
Indicates that an entity serves as an additional or supporting band associated with another primary band or musical act.
-
E.
banType
Indicates the specific category or kind of prohibition or restriction that has been applied.
- 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 6:12 p.m.