Triple
T8494110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slan |
E201050
|
entity |
| Predicate | inUniverseGroup |
P51792
|
FINISHED |
| Object | humans |
—
|
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: humans | Statement: [Slan, inUniverseGroup, humans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseGroup Context triple: [Slan, inUniverseGroup, humans]
-
A.
inUniverseOrganization
Indicates that an organization exists and operates within a specified fictional or narrative universe.
-
B.
inUniverseType
chosen
Indicates that one entity exists within, or is categorized as belonging to, a particular fictional or conceptual universe type defined by the other entity.
-
C.
inUniverseOwner
Indicates that one entity is the canonical or official owner of another entity within a specific fictional or defined universe or continuity.
-
D.
inUniverse
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
-
E.
inUniverseActivity
Indicates that an activity or event occurs within the fictional universe or narrative world of a work, rather than outside it (e.g., in real life or meta-context).
- 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe57c01f881908cb77c8c834ac08d |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:13 p.m.