Triple
T34135979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyrant |
E875566
|
entity |
| Predicate | exploresRelationshipDynamic |
P39999
|
FINISHED |
| Object | dominance and submission |
—
|
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: dominance and submission | Statement: [Tyrant, exploresRelationshipDynamic, dominance and submission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exploresRelationshipDynamic Context triple: [Tyrant, exploresRelationshipDynamic, dominance and submission]
-
A.
exploresRelationship
Indicates that one entity actively investigates, examines, or probes the nature, dynamics, or implications of its relationship with another entity.
-
B.
relationshipDynamic
chosen
Indicates a changing or evolving pattern of interaction between entities, such as shifts in their roles, closeness, or influence over time.
-
C.
exploresRomanticRelationships
Indicates that one entity engages in or investigates romantic relationships with another entity.
-
D.
coversRelationship
Indicates that one entity extends over, includes, or provides encompassing coverage for another entity or set of entities.
-
E.
showsRelationshipWith
Indicates that one entity visually or explicitly presents or demonstrates its connection or association with 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_69f349aaeef08190a20e72a3fdeb7052 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:53 a.m.