Triple
T34561155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Rock Candy Mountain |
E887343
|
entity |
| Predicate | hasBeenIncludedIn |
P56991
|
FINISHED |
| Object | folk song anthologies |
—
|
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: folk song anthologies | Statement: [Big Rock Candy Mountain, hasBeenIncludedIn, folk song anthologies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenIncludedIn Context triple: [Big Rock Candy Mountain, hasBeenIncludedIn, folk song anthologies]
-
A.
hasIncluded
Indicates that one entity has incorporated or contained another entity as part of itself or within its scope.
-
B.
formerlyIncluded
Indicates that an entity was previously part of, contained in, or a member of another entity, but is no longer included.
-
C.
initiallyIncluded
Indicates that an entity was part of a specified set, group, or configuration at the beginning of a process, period, or state.
-
D.
aimedToInclude
Indicates that one entity intentionally sought to have another entity or element contained or incorporated within it.
-
E.
includedBy
chosen
Indicates that one entity is contained within, encompassed by, or treated as a subset or member of another entity.
- 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_69f349d0c4d881908dd0950f5eb9ec0a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 1, 2026, 2:02 a.m.