Triple
T36262005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elvis (1973 album) |
E892113
|
entity |
| Predicate | hasCompilationScope |
P397
|
FINISHED |
| Object | career-spanning selection |
—
|
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: career-spanning selection | Statement: [Elvis (1973 album), hasCompilationScope, career-spanning selection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompilationScope Context triple: [Elvis (1973 album), hasCompilationScope, career-spanning selection]
-
A.
compilationScope
Indicates the range or set of elements (such as files, modules, or code units) that are included and processed together during a compilation process.
-
B.
hasRuleScope
Indicates that a rule is applicable within, or constrained to, a specific scope or context.
-
C.
hasScriptScope
Indicates that something is associated with, defined within, or limited to a particular script’s scope or execution context.
-
D.
hasScope
chosen
Indicates that one entity defines, limits, or encompasses the range, extent, or applicability within which another entity operates or is valid.
-
E.
isOnCompilation
Indicates that one entity (typically a work or item) is included as part of a compilation or collection.
- 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_69f76e4699188190af045b11a840ce31 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.