Triple
T19370508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oka coherence theorem |
E484522
|
entity |
| Predicate | typeOfCoherence |
P135681
|
FINISHED |
| Object | analytic coherence |
—
|
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: analytic coherence | Statement: [Oka coherence theorem, typeOfCoherence, analytic coherence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCoherence Context triple: [Oka coherence theorem, typeOfCoherence, analytic coherence]
-
A.
cooperatingLevel
Indicates the degree or intensity to which two or more entities are working together toward a shared goal or activity.
-
B.
cooperationType
Indicates the specific kind or form of cooperative relationship that exists between the related entities.
-
C.
concurrenceType
Indicates the specific manner or category in which two or more events, actions, or conditions occur together or overlap in time or effect.
-
D.
coerces
Indicates that one entity forces or pressures another entity to act against their will or better judgment.
-
E.
internalCohesion
Indicates the degree to which elements within a group, system, or structure are mutually connected and unified, resisting fragmentation or internal conflict.
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e619af33e481908643f8beb2f498dc |
completed | April 20, 2026, 12:18 p.m. |
| PD | Predicate disambiguation | batch_69e4fd54f8e48190956e73dd8969164a |
completed | April 19, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:35 p.m.