Triple
T2571579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regla de Ocha |
E57674
|
entity |
| Predicate | hasInitiationStage |
P9959
|
FINISHED |
| Object | asiento |
—
|
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: asiento | Statement: [Regla de Ocha, hasInitiationStage, asiento]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInitiationStage Context triple: [Regla de Ocha, hasInitiationStage, asiento]
-
A.
initiationStatus
Indicates the current state or phase of beginning or starting a process, activity, or relationship between entities.
-
B.
hasInitial
Indicates that one entity possesses or is associated with the first letter or starting character of another entity’s name or value.
-
C.
hasStep
chosen
Indicates that one entity includes, is composed of, or is associated with a specific step or stage in a process involving another entity.
-
D.
hasStageType
Indicates that an entity is associated with, or classified by, a specific type or category of stage within a process, lifecycle, or workflow.
-
E.
initiationLevels
Indicates the degree or stage at which an action, process, or relationship is begun or set in motion between entities.
- 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_69ab4a51410081908501dcf8bad9adc4 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd383dce881909411a38c6d37bc3a |
completed | March 7, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69abd0ce4dcc8190b17a65abf9bd1bb0 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.