Triple
T19177642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overlords |
E469479
|
entity |
| Predicate | relationshipToOvermind |
P134755
|
FINISHED |
| Object | subordinate race |
—
|
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: subordinate race | Statement: [Overlords, relationshipToOvermind, subordinate race]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToOvermind Context triple: [Overlords, relationshipToOvermind, subordinate race]
-
A.
relationshipToCyborg
Indicates the type or nature of a person's relational connection to a cyborg, such as familial, social, or professional.
-
B.
relationshipToDeities
Indicates how an entity is connected or related to one or more deities, such as through worship, lineage, role, or status.
-
C.
relationshipToRa
Indicates a specified type of relational connection that an entity has to the entity Ra.
-
D.
relationshipToCreature
Indicates a specified type of relational connection that one entity has toward a particular creature.
-
E.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
- 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f618f18c8190b98995fda4b6fea0 |
completed | April 20, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:07 p.m.