Triple
T11071103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orders, decorations, and medals of the Philippines |
E261746
|
entity |
| Predicate | hasGradesOrClasses |
P97643
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Orders, decorations, and medals of the Philippines, hasGradesOrClasses, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGradesOrClasses Context triple: [Orders, decorations, and medals of the Philippines, hasGradesOrClasses, yes]
-
A.
hasGrades
Indicates that an entity possesses or is associated with one or more grade values, typically reflecting evaluations or scores.
-
B.
hasNoGrades
Indicates that an entity does not possess any recorded grades or evaluations.
-
C.
hasGradeCount
Indicates a relationship where an entity is associated with the number of grades it has or has received.
-
D.
hasGradeSystem
Indicates that one entity uses, follows, or is governed by a particular grading or evaluation system defined by another entity.
-
E.
hasPossibleGrades
Indicates that an entity is associated with a set or list of grades that it can potentially receive.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79922e48c81909adb161e66f47474 |
completed | April 9, 2026, 12:18 p.m. |
| PD | Predicate disambiguation | batch_69d74411d9e881908c0eeafa0f38e4b6 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750c99f9881908ee2b01b6ce4b3a1 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:26 p.m.