Triple
T27304218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crazy Mountains |
E689003
|
entity |
| Predicate | significantTo |
P428
|
FINISHED |
| Object | Crow Nation |
—
|
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: Crow Nation | Statement: [Crazy Mountains, significantTo, Crow Nation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantTo Context triple: [Crazy Mountains, significantTo, Crow Nation]
-
A.
significantSince
Indicates that a relationship, condition, or status has held particular importance or relevance starting from a specified point in time.
-
B.
significantAfter
Indicates that one event or state occurs after another in a way that is temporally meaningful or non-trivially later, not just immediately or insignificantly afterward.
-
C.
significance
chosen
Indicates that one entity holds particular importance, influence, or meaningful impact in relation to another entity or context.
-
D.
significantPort
Indicates that a port holds major importance in terms of trade, transportation, or strategic relevance within a given context.
-
E.
significantScale
Indicates that the scale, size, or magnitude of something is notably large or important relative to a given context or standard.
- 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_69ef355b931c8190a63cafaf7bcc008b |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 11:23 a.m.