Triple
T37993218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayala |
E947872
|
entity |
| Predicate | hasRevolutionaryLeader |
P204523
|
FINISHED |
| Object | Emiliano Zapata |
E335056
|
NE 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: Emiliano Zapata | Statement: [Ayala, hasRevolutionaryLeader, Emiliano Zapata]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRevolutionaryLeader Context triple: [Ayala, hasRevolutionaryLeader, Emiliano Zapata]
-
A.
foundingLeaderOf
Indicates that an entity is the primary founder who established and initially led another entity, such as an organization, movement, or institution.
-
B.
coupLeader
Indicates that the subject is the primary organizer or head figure responsible for leading a coup against an existing authority.
-
C.
revolutionaryName
Indicates that the specified name is the one by which a revolutionary individual is known or identified.
-
D.
hasCountryLeader
Indicates that a specified country is led or governed by a particular leader (such as a president, prime minister, or monarch).
-
E.
hasContemporaryLeader
Indicates that an entity is led or governed by a leader who is current or contemporary to the entity’s time period.
- F. None of above. chosen
Provenance (5 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_69f76efa37088190be5416b7ef1ca275 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a415431a9748190861659dbba5c267b |
completed | June 28, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:20 p.m.