Triple
T6242571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quixadá |
E139638
|
entity |
| Predicate | hangGlidingSite |
P69270
|
FINISHED |
| Object | popular hang gliding takeoff 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: popular hang gliding takeoff points | Statement: [Quixadá, hangGlidingSite, popular hang gliding takeoff points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hangGlidingSite Context triple: [Quixadá, hangGlidingSite, popular hang gliding takeoff points]
-
A.
landingGLoad
Indicates the g-force experienced by an aircraft or object at the moment of landing.
-
B.
hasCliffJumping
Indicates that an entity offers, features, or is associated with the activity of cliff jumping.
-
C.
climbingArea
Indicates that one entity is a designated location or site used for climbing activities in relation to another entity.
-
D.
skiJumpingVenue
Indicates that one entity serves as the ski jumping venue or facility associated with another entity (such as an event, competition, or organization).
-
E.
landingCapability
Indicates the ability or suitability of an entity (e.g., a vehicle or system) to perform a landing under specified conditions.
- 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_69c008b1c5088190ae6de2555fc05ad8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0631933488190838b424ec0fc2155 |
completed | March 22, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c056037bf88190a0a3fe7429345d0b |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056df95ac8190bc5efe050d3af864 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:23 p.m.