Triple
T35009801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Institute (Fallout) |
E1009912
|
entity |
| Predicate | perceptionBySurface |
P182478
|
FINISHED |
| Object | mythical |
—
|
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: mythical | Statement: [The Institute (Fallout), perceptionBySurface, mythical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perceptionBySurface Context triple: [The Institute (Fallout), perceptionBySurface, mythical]
-
A.
perceptionByHumans
Indicates that something is perceived, sensed, or experienced through human sensory or cognitive processes.
-
B.
perceptionByNormals
Indicates how something is perceived, interpreted, or experienced by typical or non-exceptional observers.
-
C.
isSurfaceSensitive
Indicates that the property, behavior, or measurement depends strongly on the characteristics or condition of a surface rather than the bulk material.
-
D.
surfaceType
Indicates the kind or classification of surface associated with an entity or interaction.
-
E.
viewOnPerception
Indicates a relationship where one entity expresses or embodies a particular stance, interpretation, or opinion about the nature or process of perception.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78dbf72648190a4971a558e9d1889 |
completed | May 3, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78ce43094819093857fc99f269afe |
completed | May 3, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4:01 p.m.