Triple
T26639433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Si Trail |
E668734
|
entity |
| Predicate | isSmallerCompanionOf |
P126949
|
FINISHED |
| Object | Mount Si |
—
|
NE NERFINISHED |
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: Mount Si | Statement: [Little Si Trail, isSmallerCompanionOf, Mount Si]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSmallerCompanionOf Context triple: [Little Si Trail, isSmallerCompanionOf, Mount Si]
-
A.
companionOf
Indicates that one entity serves as a companion or partner to another, typically accompanying or being closely associated with them.
-
B.
hasSmallerCounterpart
chosen
Indicates that one entity has another entity as its corresponding version that is smaller in size, scale, or magnitude.
-
C.
wasCompanionOf
Indicates that one entity accompanied or associated closely with another, typically as a partner, ally, or fellow participant over some period of time.
-
D.
includesCompanion
Indicates that one entity involves, contains, or is accompanied by another entity acting as a companion.
-
E.
hasCompanionSpecies
Indicates that one entity is accompanied by, or exists in association with, another entity of a different species.
- 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_69ee9d0024b8819090a7c8cf669a3b6c |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 2:28 a.m.