Triple
T31208895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Our Goal, Our Effort, Our Direction |
E795679
|
entity |
| Predicate | programmaticRole |
P65172
|
FINISHED |
| Object | programmatic outline of Sokol goals |
—
|
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: programmatic outline of Sokol goals | Statement: [Our Goal, Our Effort, Our Direction, programmaticRole, programmatic outline of Sokol goals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programmaticRole Context triple: [Our Goal, Our Effort, Our Direction, programmaticRole, programmatic outline of Sokol goals]
-
A.
providedRole
Indicates that one entity has assigned or supplied a specific role or function to another entity.
-
B.
codeRole
Indicates a relationship where an entity serves a specific role or function within a piece of code or software system.
-
C.
programmatic
Indicates that one entity is created, controlled, or executed through code or automated software instructions rather than through manual or interactive means.
-
D.
scriptCodeRole
Indicates the role or function that a particular script code plays within a given context or system.
-
E.
hasProceduralRole
chosen
Indicates that an entity participates in a process or procedure by fulfilling a specific functional role within that process.
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 29, 2026, 9:09 p.m.