Triple
T20697446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen of the Morlocks |
E508692
|
entity |
| Predicate | connectedToGroup |
P92679
|
FINISHED |
| Object | underground-dwelling Morlock community |
—
|
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: underground-dwelling Morlock community | Statement: [Queen of the Morlocks, connectedToGroup, underground-dwelling Morlock community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToGroup Context triple: [Queen of the Morlocks, connectedToGroup, underground-dwelling Morlock community]
-
A.
connectedToOrganization
Indicates that an entity has a relationship or association with a particular organization, such as membership, affiliation, or formal linkage.
-
B.
memberOfGroupWith
chosen
Indicates that an entity belongs to, or is associated as a member with, a particular group or collection of entities.
-
C.
connectedToEvent
Indicates that an entity has a direct association or linkage with a specific event.
-
D.
connectionTo
Indicates a relationship in which one entity is linked, associated, or otherwise related to another entity.
-
E.
interactsWithGroup
Indicates that an entity engages in actions or exchanges with a collective group of 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_69e0b4c2b2a481909e31e9cb8f81ab55 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6c1132178819081086e085f7b3ff8 |
completed | April 21, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:11 p.m.