Triple
T8318963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the shining (psychic ability) |
E194778
|
entity |
| Predicate | canBeDetectedBy |
P80146
|
FINISHED |
| Object | other people with the shining |
—
|
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: other people with the shining | Statement: [the shining (psychic ability), canBeDetectedBy, other people with the shining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeDetectedBy Context triple: [the shining (psychic ability), canBeDetectedBy, other people with the shining]
-
A.
detectorType
Indicates the specific kind or category of detector associated with an entity or measurement.
-
B.
detected
Indicates that an entity has observed, identified, or discovered the presence or occurrence of another entity or event.
-
C.
canBeMonitoredWith
chosen
Indicates that one entity is suitable or able to be observed, tracked, or supervised using another specified entity or method.
-
D.
canBeSeenWith
Indicates that two entities are observable together in the same context, setting, or time.
-
E.
detectorConcept
Indicates that one entity functions as a detector whose conceptual design, type, or detection principle is characterized or specified by the other 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_69ca82e7a8a88190a32bb5cc0feb012d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f648e10819081ad1fed870b2b86 |
completed | March 31, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69cb70bf689c8190a9d9b6b872abf53d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:55 p.m.