Triple
T17817456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maitland Airport |
E444883
|
entity |
| Predicate | hasBasedActivity |
P129015
|
FINISHED |
| Object | aerobatic flying |
—
|
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: aerobatic flying | Statement: [Maitland Airport, hasBasedActivity, aerobatic flying]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBasedActivity Context triple: [Maitland Airport, hasBasedActivity, aerobatic flying]
-
A.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
B.
hasAct
Indicates that an entity performs, participates in, or is associated with a specific act or action.
-
C.
hasSubjectActivity
Indicates that an entity is associated with or participates in a particular activity as its subject.
-
D.
hasPublicActivity
Indicates that an entity engages in actions or behaviors that are visible or accessible to the general public.
-
E.
hasSignificantActivity
Indicates that an entity exhibits a notable level or intensity of activity, performance, or operation relative to a defined threshold or context.
- 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48880457c81908214741d6cd7a1ee |
completed | April 19, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:14 a.m.