Triple
T26085997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RRC |
E657982
|
entity |
| Predicate | hasGradeRelation |
P163710
|
FINISHED |
| Object | Associate of the Royal Red Cross (ARRC) |
—
|
NE NERFINISHED |
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: Associate of the Royal Red Cross (ARRC) | Statement: [RRC, hasGradeRelation, Associate of the Royal Red Cross (ARRC)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGradeRelation Context triple: [RRC, hasGradeRelation, Associate of the Royal Red Cross (ARRC)]
-
A.
hasGradeStatus
Indicates that an entity holds a particular grade-related status or standing within an evaluation or grading system.
-
B.
atGradeRelation
Indicates that one entity is positioned at the same grade or elevation level as another entity.
-
C.
hasGradeType
Indicates that an entity is associated with a particular category or type of grade (e.g., letter grade, pass/fail, percentage).
-
D.
hasGradeCount
Indicates a relationship where an entity is associated with the number of grades it has or has received.
-
E.
hasGrades
Indicates that an entity possesses or is associated with one or more grade values, typically reflecting evaluations or scores.
- 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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6397b64f881909d811225e57aac5e |
completed | May 2, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f638d029148190877c103f0eeaf147 |
completed | May 2, 2026, 5:48 p.m. |
Created at: April 26, 2026, 7:43 p.m.