Triple
T4568649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ornithology |
E121973
|
entity |
| Predicate | commonlyIncludedIn |
P46711
|
FINISHED |
| Object | jazz jam session repertoire |
—
|
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: jazz jam session repertoire | Statement: [Ornithology, commonlyIncludedIn, jazz jam session repertoire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyIncludedIn Context triple: [Ornithology, commonlyIncludedIn, jazz jam session repertoire]
-
A.
commonlyFoundOn
Indicates that one entity is typically or frequently located on, attached to, or present upon another entity.
-
B.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
C.
isFrequentlyIncludedIn
chosen
Indicates that something is regularly or commonly contained or made part of something else.
-
D.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
E.
widelyUsedIn
Indicates that something is commonly or extensively utilized within a particular context, domain, or group.
- 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_69bd463f156881908a99aca69c5721ac |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58a0dfbc81909b5023f0c29addaf |
completed | March 20, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69bd5227063c8190973155a875b013a7 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.