Triple
T19439477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ignacio López Rayón |
E486306
|
entity |
| Predicate | joinedInsurgentMovement |
P12161
|
FINISHED |
| Object | 1810 |
—
|
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: 1810 | Statement: [Ignacio López Rayón, joinedInsurgentMovement, 1810]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinedInsurgentMovement Context triple: [Ignacio López Rayón, joinedInsurgentMovement, 1810]
-
A.
joinedRebellion
chosen
Indicates that an entity became a member or active participant in a rebellion against an established authority.
-
B.
memberOfPoliticalMovement
Indicates that an entity belongs to, supports, or participates in a specific political movement.
-
C.
insurgentSupporter
Indicates that one entity supports, assists, or aligns with an insurgent group or insurgent activities.
-
D.
associatedWithRebelGroup
Indicates that one entity is connected or linked in some capacity to a rebel group, such as through membership, support, collaboration, or affiliation.
-
E.
enlistedIn
Indicates that an individual has formally joined and is serving in a particular military or service organization.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633637ea48190bfa36b0b0a2762bc |
completed | April 20, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.