Triple
T9514716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokens of Trust |
E229493
|
entity |
| Predicate | intendsTo |
P88492
|
FINISHED |
| Object | explain Christian creeds |
—
|
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: explain Christian creeds | Statement: [Tokens of Trust, intendsTo, explain Christian creeds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendsTo Context triple: [Tokens of Trust, intendsTo, explain Christian creeds]
-
A.
intendedWith
Indicates that one entity is the planned or desired target, recipient, or context for the use or application of another entity.
-
B.
typicalIntentionsInclude
Indicates that one entity’s usual or characteristic intentions encompass or include the other entity or action.
-
C.
intendedToCreate
Indicates that one entity performed an action or was designed with the purpose or goal of bringing another entity into existence or causing it to come about.
-
D.
patronIntention
Indicates that a patron has a specific intended action, purpose, or goal directed toward another entity or activity.
-
E.
intendedProject
Indicates that an entity is the planned or targeted project associated with another entity (such as a person, organization, or activity).
- 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_69ca84777560819084cddd999badc1aa |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd986bfcac8190aa97f8975cb17f6c |
completed | April 1, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cca567ca448190bf4bcce8ce7dd54f |
completed | April 1, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69cca89d0f0c8190b4528990fe708fca |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:58 p.m.