Triple
T28853261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lamberts Point coal terminal |
E728661
|
entity |
| Predicate | handlesFrom |
P169970
|
FINISHED |
| Object | Appalachian mines |
—
|
NE NERFINISHED |
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: Appalachian mines | Statement: [Lamberts Point coal terminal, handlesFrom, Appalachian mines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesFrom Context triple: [Lamberts Point coal terminal, handlesFrom, Appalachian mines]
-
A.
handles
Indicates that one entity is responsible for dealing with, managing, or taking care of another entity or task.
-
B.
usesHandle
Indicates that an entity operates, controls, or interacts with another entity by means of a handle or handled interface.
-
C.
handledWith
Indicates that an entity is managed, processed, or dealt with using a particular method, tool, or means.
-
D.
handlingProperty
Indicates that one entity specifies how another entity should be handled, processed, or treated under certain conditions.
-
E.
handledIn
Indicates that an action, request, or process is managed, processed, or resolved within a particular context, location, system, or jurisdiction.
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f688d015908190ad5df37030ecf332 |
completed | May 2, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 28, 2026, 6:44 a.m.