Triple
T27782555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hill Valley Clock Tower |
E699370
|
entity |
| Predicate | hasInUniverseMaterial |
P83340
|
FINISHED |
| Object | stone |
—
|
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: stone | Statement: [Hill Valley Clock Tower, hasInUniverseMaterial, stone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInUniverseMaterial Context triple: [Hill Valley Clock Tower, hasInUniverseMaterial, stone]
-
A.
inUniverseMaterial
chosen
Indicates that something is made of or composed from a material that exists within a specified fictional or conceptual universe.
-
B.
hasMaterialResource
Indicates that an entity possesses, controls, or has access to a tangible material resource.
-
C.
hasFictionalUniverseElement
Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
-
D.
hasMaterialRole
Indicates that an entity participates in an activity or context by fulfilling a specific material-related role or function.
-
E.
hasLanternMaterial
Indicates that an entity’s lantern is made from or composed of a specified material.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: April 27, 2026, 5:11 p.m.