Triple
T6363268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Club |
E143162
|
entity |
| Predicate | statusQualificationMethod |
P750
|
FINISHED |
| Object | miles flown |
—
|
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: miles flown | Statement: [Royal Club, statusQualificationMethod, miles flown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusQualificationMethod Context triple: [Royal Club, statusQualificationMethod, miles flown]
-
A.
statusQualificationMetric
Indicates a metric that qualifies, evaluates, or characterizes the status or condition of something in a measurable way.
-
B.
assessmentMethod
chosen
Indicates the method or procedure used to evaluate, measure, or judge something.
-
C.
hasQualification
Indicates that an entity possesses a specific qualification, credential, or competency.
-
D.
qualificationProcess
Indicates the process or set of steps through which an entity is evaluated and approved as meeting required qualifications or standards.
-
E.
hasQualificationStructure
Indicates that an entity is associated with a specific configuration or pattern of qualifications (e.g., degrees, certifications, or credentials) that define how those qualifications are organized or structured.
- 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_69c008d7a9c4819098d647ec47776917 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0680d51a4819098a6bcd3dfd73be4 |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060ee055081908c79a1d151bd74cd |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:32 p.m.