Triple
T12607378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ordre de la Sincérité |
E301016
|
entity |
| Predicate | gradeSystem |
P48042
|
FINISHED |
| Object | single class (originally) |
—
|
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: single class (originally) | Statement: [Ordre de la Sincérité, gradeSystem, single class (originally)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gradeSystem Context triple: [Ordre de la Sincérité, gradeSystem, single class (originally)]
-
A.
gradingSystem
chosen
Indicates the method or criteria by which performance, quality, or achievement is evaluated and assigned a grade or score.
-
B.
gradeNumber
Indicates the numerical grade or level assigned to an entity within an ordered grading or classification system.
-
C.
grades
Indicates that one entity evaluates and assigns a score or level of performance to another entity.
-
D.
gradeSeparated
Indicates that two intersecting transportation routes are physically separated by different elevation levels so they do not cross at the same grade.
-
E.
gradeRank
Indicates the relative academic standing or position of an entity within a graded or ranked group based on performance or scores.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9559458dc8190bc4d6e697e99d70e |
completed | April 10, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69d9541894fc8190a0c3706a414279f0 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:11 p.m.