Triple
T9997621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alex Martin |
E197239
|
entity |
| Predicate | strandedLocationType |
P91496
|
FINISHED |
| Object | remote mountain wilderness |
—
|
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: remote mountain wilderness | Statement: [Alex Martin, strandedLocationType, remote mountain wilderness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strandedLocationType Context triple: [Alex Martin, strandedLocationType, remote mountain wilderness]
-
A.
landfallLocation
Indicates the geographic location where a storm or similar weather system first makes landfall.
-
B.
beachedAt
Indicates that something has come ashore and is stranded or resting on a beach at a particular location or time.
-
C.
rescuedLocation
Indicates the place where a rescue action occurred or from which someone or something was rescued.
-
D.
survivorsLandingPlace
Indicates the location where survivors arrived or were brought after an incident or event.
-
E.
landedNear
Indicates that one entity has come to rest on a surface or location in close proximity to another specified entity or reference point.
- 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_69ca82f3b61c81908ecc2c1c96dbc2e4 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdcc8aa1a881909879a694496f11a5 |
completed | April 2, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69cd1da07db88190945bcdab3ca82e71 |
completed | April 1, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69cd358386f48190833c862b5b8c04b2 |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:51 p.m.