Triple
T38196030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falcon SuperChair |
E1005612
|
entity |
| Predicate | terrainDifficultyServed |
P43109
|
FINISHED |
| Object | advanced |
—
|
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: advanced | Statement: [Falcon SuperChair, terrainDifficultyServed, advanced]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terrainDifficultyServed Context triple: [Falcon SuperChair, terrainDifficultyServed, advanced]
-
A.
hasTrailDifficulty
Indicates the level of challenge or effort required to traverse a particular trail or route.
-
B.
hasBeginnerTerrain
chosen
Indicates that something provides or includes terrain or areas suitable for beginners.
-
C.
raidDifficultyAvailability
Indicates how the availability or accessibility of a raid changes based on its selected difficulty level.
-
D.
terrainNavigation
Indicates the ability or process of moving through, over, or across different types of terrain or ground conditions.
-
E.
difficultySource
Indicates that one entity is the cause, origin, or contributing factor to the difficulty or challenge experienced in relation to another entity or situation.
- 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_69f76dbd22f48190940318cea061e8bb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:29 p.m.