Triple
T27943196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Levels Depot, West Virginia |
E700810
|
entity |
| Predicate | hasNearbyCommunities |
P4647
|
FINISHED |
| Object | Levels, West Virginia |
—
|
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: Levels, West Virginia | Statement: [Levels Depot, West Virginia, hasNearbyCommunities, Levels, West Virginia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyCommunities Context triple: [Levels Depot, West Virginia, hasNearbyCommunities, Levels, West Virginia]
-
A.
hasNearbyCommunity
chosen
Indicates that one entity has another community located close to it in geographic or spatial terms.
-
B.
hasLocalCommunities
Indicates that an entity is associated with or contains smaller, localized community groups within a specific area or region.
-
C.
hasRemoteCommunities
Indicates that an entity maintains or is associated with communities located in distant or geographically isolated areas.
-
D.
hasCommunityArea
Indicates that an entity is associated with, located in, or belongs to a particular community area.
-
E.
hasCommunesNear
Indicates that one entity has communes located in its nearby geographic vicinity.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: April 27, 2026, 7:19 p.m.