Triple
T6741511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iona Community |
E154092
|
entity |
| Predicate | coreCommitment |
P72694
|
FINISHED |
| Object | peace |
—
|
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: peace | Statement: [Iona Community, coreCommitment, peace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreCommitment Context triple: [Iona Community, coreCommitment, peace]
-
A.
commitment
Indicates a sustained obligation or promise that binds an entity to a course of action, relationship, or goal over time.
-
B.
commitmentGrade
Indicates the level or quality of commitment one entity has made toward another entity or agreed-upon action.
-
C.
typicalCommitment
Indicates a standard or commonly expected level of obligation or promise that one entity holds toward another or toward performing an action.
-
D.
guaranteeCommitments
Indicates a relationship where one party formally assures that specific obligations or promises made to another party will be fulfilled or upheld.
-
E.
commitmentTiming
Indicates the point in time or period relative to an event or agreement when a commitment is made, becomes effective, or is expected to be fulfilled.
- 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_69c6880d84d8819095d19de2295f26ac |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d1b245988190a9d5260f4872bbea |
completed | March 27, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69c6d09067a0819087ed6c820f4699f8 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d14e18d481908aaac34897c650f1 |
completed | March 27, 2026, 6:49 p.m. |
Created at: March 27, 2026, 2:10 p.m.