Triple
T6651897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paps of Jura |
E150840
|
entity |
| Predicate | requiresNavigationSkills |
P6204
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Paps of Jura, requiresNavigationSkills, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresNavigationSkills Context triple: [Paps of Jura, requiresNavigationSkills, true]
-
A.
requiresSkill
chosen
Indicates that performing or engaging in one entity (e.g., a task or role) depends on possessing or applying a specific skill represented by the other entity.
-
B.
requiresSkillLevel
Indicates that performing or engaging in something depends on possessing at least a specified level of skill.
-
C.
hasNavigationKnowledge
Indicates that an entity possesses information or expertise related to navigating or determining routes within an environment or system.
-
D.
requiresPractice
Indicates that performing or mastering one entity depends on engaging in repeated practice or training involving another entity.
-
E.
servesSkillLevel
Indicates that one entity provides or is appropriate for a particular level of skill in another entity.
- 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_69c687f2c9508190a60b9aad31d3f358 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad071b0081909b96dd4b93414bd1 |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:01 p.m.