Triple
T5407823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brenva Spur |
E120935
|
entity |
| Predicate | hasCommitmentGrade |
P27619
|
FINISHED |
| Object | high commitment |
—
|
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: high commitment | Statement: [Brenva Spur, hasCommitmentGrade, high commitment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommitmentGrade Context triple: [Brenva Spur, hasCommitmentGrade, high commitment]
-
A.
commitmentGrade
chosen
Indicates the level or quality of commitment one entity has made toward another entity or agreed-upon action.
-
B.
hasGrades
Indicates that an entity possesses or is associated with one or more grade values, typically reflecting evaluations or scores.
-
C.
hasGradeCount
Indicates a relationship where an entity is associated with the number of grades it has or has received.
-
D.
isGradeWithin
Indicates that a given grade value falls within a specified acceptable or defined grade range.
-
E.
isGradedBy
Indicates that an entity (such as an assignment, exam, or work) is evaluated and assigned a grade by another entity (such as a person, system, or organization).
- 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_69bd46391c0c81909fa484446732b6a3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8793ab3c81909992b257d462a554 |
completed | March 20, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69bd8467e6b48190b9eaa9de67072e06 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.