Triple
T4807224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heart of Gold |
E106975
|
entity |
| Predicate | usesPrimaryKey |
P60234
|
FINISHED |
| Object | G major |
—
|
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: G major | Statement: [Heart of Gold, usesPrimaryKey, G major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPrimaryKey Context triple: [Heart of Gold, usesPrimaryKey, G major]
-
A.
primaryIndex
Indicates that one entity serves as the main or default index used to organize, access, or reference another entity within a system or dataset.
-
B.
hasPrimarySee
Indicates that one entity is designated as the main or preferred "see" reference or cross-reference for another entity.
-
C.
primaryReference
Indicates that one entity serves as the main or authoritative source of information or citation for another entity.
-
D.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
-
E.
primaryReferent
Indicates that one entity is the main or most salient referent associated with another entity among potentially multiple candidates.
- 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_69bd43f6a1e08190bf0a372bfc336ee5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1c43a48190a65e56b1624a2339 |
completed | March 20, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69bd6ff731188190a9903602122d4ff9 |
completed | March 20, 2026, 4:04 p.m. |
Created at: March 20, 2026, 1:23 p.m.