Triple
T4677336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kasterborous |
E103712
|
entity |
| Predicate | hasInUniverseRole |
P58964
|
FINISHED |
| Object | home stellar system of the Time Lords |
—
|
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: home stellar system of the Time Lords | Statement: [Kasterborous, hasInUniverseRole, home stellar system of the Time Lords]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInUniverseRole Context triple: [Kasterborous, hasInUniverseRole, home stellar system of the Time Lords]
-
A.
hasFictionalRole
Indicates that an entity plays or is assigned a specific role within a fictional work or narrative.
-
B.
hasCrewRole
Indicates that an entity serves in a specific role or position within a crew associated with another entity.
-
C.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or context.
-
D.
hasPlayedRole
Indicates that an entity has performed or portrayed a particular role or character in some context (such as a film, play, or production).
-
E.
hasMainRole
Indicates that an entity holds the primary or most significant role in relation to another entity or context.
- 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_69bd43dda32c8190938b37744ca270fc |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd67c9c3c08190a6c4944cdd1362a8 |
completed | March 20, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69bd6217e0088190836570522e324dc6 |
completed | March 20, 2026, 3:04 p.m. |
| PDg | Predicate description generation | batch_69bd67c895dc8190ba648002ff54424b |
completed | March 20, 2026, 3:29 p.m. |
Created at: March 20, 2026, 1:16 p.m.