Triple
T13089883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Segundo Frente |
E310432
|
entity |
| Predicate | hasRevolutionaryHeritage |
P107990
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Segundo Frente, hasRevolutionaryHeritage, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRevolutionaryHeritage Context triple: [Segundo Frente, hasRevolutionaryHeritage, yes]
-
A.
hasHistoricSignificanceFor
Indicates that something holds notable historical importance or relevance for a particular entity or group.
-
B.
hasHistoricalSignificance
Indicates that something possesses notable importance or influence within a historical context or period.
-
C.
revolutionaryName
Indicates that the specified name is the one by which a revolutionary individual is known or identified.
-
D.
revolutionaryBody
Indicates a body or organization that leads, governs, or coordinates a revolutionary movement or uprising.
-
E.
hasHeritage
Indicates that an entity possesses or is associated with a particular cultural, ethnic, or ancestral background.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d98138a1d481908a139f2f67eb3472 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d98114a6508190b1e8e018bb5a068c |
completed | April 10, 2026, 11 p.m. |
Created at: April 9, 2026, 9:03 p.m.