Triple
T27853811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batalla de Las Piedras |
E704029
|
entity |
| Predicate | marcaHito |
P52327
|
FINISHED |
| Object | consolidación del liderazgo de José Gervasio Artigas |
—
|
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: consolidación del liderazgo de José Gervasio Artigas | Statement: [Batalla de Las Piedras, marcaHito, consolidación del liderazgo de José Gervasio Artigas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marcaHito Context triple: [Batalla de Las Piedras, marcaHito, consolidación del liderazgo de José Gervasio Artigas]
-
A.
marque
Indicates that one entity is the brand or make associated with another entity, such as a product, vehicle, or manufactured item.
-
B.
hitsMilestone
chosen
Indicates that an entity reaches or achieves a predefined milestone or target in a process, project, or progression.
-
C.
marksOn
Indicates that one entity bears visible signs, traces, or imprints that have been made or left by another entity.
-
D.
marked
Indicates that one entity has been identified, labeled, or highlighted in some way by another entity.
-
E.
markType
Indicates the specific category or kind of mark associated with or applied to an 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_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. |
Created at: April 27, 2026, 6:12 p.m.