Triple
T29239571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | discography of Gary Numan |
E741281
|
entity |
| Predicate | hasSecondaryFormat |
P196148
|
FINISHED |
| Object | video recording |
—
|
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: video recording | Statement: [discography of Gary Numan, hasSecondaryFormat, video recording]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryFormat Context triple: [discography of Gary Numan, hasSecondaryFormat, video recording]
-
A.
hasSecondary
Indicates that an entity is associated with an additional or subordinate counterpart beyond its primary one.
-
B.
hasSecondaryUsage
Indicates that an entity is associated with an additional, non-primary function or purpose beyond its main intended use.
-
C.
hasSecondaryBase
Indicates that an entity possesses or is associated with a secondary or additional base, distinct from its primary base.
-
D.
hasSecondaryComponent
Indicates that an entity includes or is associated with an additional, subordinate component beyond its primary one.
-
E.
hasSecondarySource
Indicates that an entity is supported, documented, or referenced by a secondary source rather than by a primary or original source.
- F. None of above. chosen
Provenance (4 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_69f0911dd6fc819097d1abb287016489 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fe0d165a48819098b854318a50d76c |
completed | May 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69fe0931002481908a95b34f95e9f64e |
completed | May 8, 2026, 4:02 p.m. |
| PDg | Predicate description generation | batch_69fe0d14778c8190986fa4f37f992a2f |
completed | May 8, 2026, 4:19 p.m. |
Created at: April 28, 2026, 12:30 p.m.