Triple
T13751900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grizzly Ridge |
E330372
|
entity |
| Predicate | includesContentAbout |
P86949
|
FINISHED |
| Object | grizzly bear diet |
—
|
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: grizzly bear diet | Statement: [Grizzly Ridge, includesContentAbout, grizzly bear diet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesContentAbout Context triple: [Grizzly Ridge, includesContentAbout, grizzly bear diet]
-
A.
textsIncludedIn
Indicates that certain texts are contained within, or form a subset of, a larger collection or body of texts.
-
B.
containsDataAbout
chosen
Indicates that one entity holds or includes information or records pertaining to another entity.
-
C.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
D.
contentAccess
Indicates that one entity is permitted to retrieve, view, or otherwise use the content provided or controlled by another entity.
-
E.
typicallyContain
Indicates that one entity is normally or commonly found within, included in, or held by another entity under usual circumstances.
- 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_69d81c573f288190aa2403d484fa3d49 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0215cfa08190aaed8b089aff217b |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:09 p.m.