Triple
T27853800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batalla de Las Piedras |
E704029
|
entity |
| Predicate | bando1 |
P163418
|
FINISHED |
| Object | fuerzas independentistas orientales |
—
|
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: fuerzas independentistas orientales | Statement: [Batalla de Las Piedras, bando1, fuerzas independentistas orientales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bando1 Context triple: [Batalla de Las Piedras, bando1, fuerzas independentistas orientales]
-
A.
bando
Indicates a relationship where an entity is placed under a ban, prohibition, or outlaw status imposed by some authority.
-
B.
banType
Indicates the specific category or kind of prohibition or restriction that has been applied.
-
C.
B_1
Indicates that one entity is the first or primary instance/member in an ordered series or group relative to another entity.
-
D.
BOIC
Indicates a relationship where one entity is the beneficiary or intended recipient of an item, action, or outcome provided or directed by another entity.
-
E.
banhadaPelo
Indicates that one entity is bathed or washed 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6390683448190949ddbbde9f1d385 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6359d46b88190922dd7de508e3b0e |
completed | May 2, 2026, 5:34 p.m. |
Created at: April 27, 2026, 6:12 p.m.