Triple
T5442647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dynasty (TV series) theme |
E122171
|
entity |
| Predicate | hasPrimaryKey |
P64102
|
FINISHED |
| Object | minor key (general) |
—
|
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: minor key (general) | Statement: [Dynasty (TV series) theme, hasPrimaryKey, minor key (general)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryKey Context triple: [Dynasty (TV series) theme, hasPrimaryKey, minor key (general)]
-
A.
usesPrimaryKey
Indicates that one entity relies on or references another entity’s primary key as its main means of identification or linkage.
-
B.
hasIndex
Indicates that one entity serves as an index or positional reference for another entity within an ordered collection or structure.
-
C.
hasPrimarySee
Indicates that one entity is designated as the main or preferred "see" reference or cross-reference for another entity.
-
D.
hasPrimaryPool
Indicates that an entity is associated with or designated to use a particular pool as its main or default pool.
-
E.
hasPrimitiveRelation
Indicates a basic, direct relationship between entities that is not derived from or dependent on any other relations.
- 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_69bd46400768819092925d461c0b8432 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd922f66bc8190b7d47fd68d2fcf2e |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd919aeb048190b786f814177d6cd9 |
completed | March 20, 2026, 6:27 p.m. |
| PDg | Predicate description generation | batch_69bd922dc688819092bf33589ebc6d50 |
completed | March 20, 2026, 6:30 p.m. |
Created at: March 20, 2026, 2:07 p.m.