Triple
T5722765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AerClub |
E126185
|
entity |
| Predicate | programFeature |
P66086
|
FINISHED |
| Object | tier points |
—
|
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: tier points | Statement: [AerClub, programFeature, tier points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programFeature Context triple: [AerClub, programFeature, tier points]
-
A.
programmingFeature
Indicates a relationship where one entity is a specific programming-related capability, construct, or functionality provided or supported by another entity (such as a language, tool, or system).
-
B.
featuresFictionalProgram
Indicates that a work includes or presents a fictional program (such as a TV show, software, or in-universe broadcast) as part of its content.
-
C.
programContent
Indicates that a program includes or is composed of specific content elements or materials.
-
D.
scriptFeature
Indicates that a script includes, supports, or is characterized by a particular feature or capability.
-
E.
programIncluded
Indicates that a particular program is contained within, or forms part of, another specified collection, package, or set of programs.
- 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_69c0082f723881908ce8bb13a0c0f8b7 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c47f4c81909e6849c3be3e951c |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c028fec2bc819083f5dca6a8d9d435 |
completed | March 22, 2026, 5:38 p.m. |
Created at: March 22, 2026, 3:46 p.m.