Triple
T9999705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Master of the Universe |
E197291
|
entity |
| Predicate | containsRelationshipType |
P10690
|
FINISHED |
| Object | dominant–submissive 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: dominant–submissive relationship | Statement: [Master of the Universe, containsRelationshipType, dominant–submissive relationship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsRelationshipType Context triple: [Master of the Universe, containsRelationshipType, dominant–submissive relationship]
-
A.
hasSymbolicRelationshipType
Indicates that there exists a symbolic (non-literal) relationship of a specified type between two entities.
-
B.
hasCentralRelationshipType
Indicates that there exists a primary or most significant type of relationship that characterizes how two entities are related to each other.
-
C.
hasRelation
Indicates that there exists some specified relationship or association between two entities.
-
D.
relationshipType
chosen
Indicates the specific kind of relationship that exists between two or more entities.
-
E.
hasKeyRelationship
Indicates a relationship where one entity serves as a key (e.g., identifier, access token, or primary reference) that grants access to, controls, or uniquely identifies another entity.
- 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_69ca82f3b61c81908ecc2c1c96dbc2e4 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdcc8dc9c081909b6d20909ada09cf |
completed | April 2, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69cd1da2cf9081908a6c0eb5247d0bc2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:51 p.m.