Triple
T16903671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | king crab safaris |
E424501
|
entity |
| Predicate | experienceFeatures |
P57711
|
FINISHED |
| Object | Arctic scenery |
—
|
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: Arctic scenery | Statement: [king crab safaris, experienceFeatures, Arctic scenery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: experienceFeatures Context triple: [king crab safaris, experienceFeatures, Arctic scenery]
-
A.
experienceFeature
chosen
Indicates that an entity undergoes, encounters, or makes use of a particular feature.
-
B.
featuresIn
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
-
C.
providesExperienceOf
Indicates that one entity enables or delivers the experience of another entity to someone or something.
-
D.
experienceStyle
Indicates that one entity has or is associated with a particular manner, approach, or style in which an experience is delivered or undergone.
-
E.
experiences
Indicates that an entity undergoes, feels, or is affected by a particular event, state, or condition.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3c8de3070819085bfe9696bc887ea |
completed | April 18, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.