Triple
T1473164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of the worlds |
E27180
|
entity |
| Predicate | expressesRelationship |
P10690
|
FINISHED |
| Object | Creator-creation relationship |
—
|
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: Creator-creation relationship | Statement: [Lord of the worlds, expressesRelationship, Creator-creation relationship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expressesRelationship Context triple: [Lord of the worlds, expressesRelationship, Creator-creation relationship]
-
A.
relationshipType
chosen
Indicates the specific kind of relationship that exists between two or more entities.
-
B.
portraysRelationship
Indicates that one entity depicts, represents, or illustrates a relationship between other entities.
-
C.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
-
D.
semanticRelation
Indicates a general meaning-based connection between two entities, such as similarity, implication, or conceptual association.
-
E.
definesRelationshipBetween
Indicates that one entity specifies or establishes the nature, type, or rules of a relationship that exists between two or more other entities.
- 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_69a496d25d6881909dbd84f86d763992 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c5dc90e481908a4935f266bc7850 |
completed | March 1, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69a4c48350d88190a81bd149103f93e3 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:01 p.m.