Triple
T5336924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toribio Montes |
E123848
|
entity |
| Predicate | movementSuppressed |
P62915
|
FINISHED |
| Object | early independence movements in Quito region |
—
|
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: early independence movements in Quito region | Statement: [Toribio Montes, movementSuppressed, early independence movements in Quito region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementSuppressed Context triple: [Toribio Montes, movementSuppressed, early independence movements in Quito region]
-
A.
movementStatus
Indicates the current state or condition of an entity’s movement, such as whether and how it is moving or stationary.
-
B.
usesMovement
Indicates that an entity performs or involves some form of movement as part of its action or behavior.
-
C.
movementSupported
Indicates that an entity’s movement is enabled, facilitated, or allowed by another entity or system.
-
D.
movementPeriod
Indicates the span of time during which a movement or motion occurs or is valid.
-
E.
movementCause
Indicates that one entity’s action or event is the cause of another entity’s movement or change in location.
- 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_69bd464b07f8819095aa76577c9829e4 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85b104c081908b81236a0142e1c8 |
completed | March 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69bd84583dbc819088a03e3afb30178c |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd8501d53c81908371bd5195ba5703 |
completed | March 20, 2026, 5:33 p.m. |
Created at: March 20, 2026, 2 p.m.