Triple
T36817997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dave Morgan |
E909798
|
entity |
| Predicate | initiallyDiscovers |
P31387
|
FINISHED |
| Object | Link in a block of ice |
—
|
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: Link in a block of ice | Statement: [Dave Morgan, initiallyDiscovers, Link in a block of ice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initiallyDiscovers Context triple: [Dave Morgan, initiallyDiscovers, Link in a block of ice]
-
A.
hasDiscovered
chosen
Indicates that one entity has found, detected, or uncovered the existence, presence, or truth of another entity or phenomenon.
-
B.
discoveredAs
Indicates that one entity was first identified, found, or recognized in the role or form specified by another entity.
-
C.
discovery
Indicates the event or process by which one entity finds, uncovers, or identifies something previously unknown or unrecognized.
-
D.
namedForDiscoveryOf
Indicates that one entity is named in recognition of another entity’s discovery of something.
-
E.
discoveryTarget
Indicates that one entity is the object, subject, or focus that another entity discovers or aims to discover.
- 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_69f76e7dd13c81908c60b05adb49eeb5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: May 3, 2026, 4:13 p.m.