Triple
T29576010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titan |
E753444
|
entity |
| Predicate | associatedWithKey |
P148502
|
FINISHED |
| Object | D 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: D major | Statement: [Titan, associatedWithKey, D major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithKey Context triple: [Titan, associatedWithKey, D major]
-
A.
associatedKey
chosen
Indicates that one entity serves as a key or identifier that is logically or functionally linked to another entity.
-
B.
associatedWithAssociation
Indicates a relationship where an entity is linked or connected to a particular association or organization.
-
C.
associatedWithRelationship
Indicates a general connection or involvement between entities through some form of relationship, without specifying its exact nature.
-
D.
associatedWithAttribute
Indicates that one entity is linked to, characterized by, or described through a particular attribute.
-
E.
associatedWithStrategy
Indicates that an entity has a connection or involvement with a particular strategy, such as contributing to, being guided by, or aligned with that strategy.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 28, 2026, 6:03 p.m.