Triple
T30917533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stage Island |
E787621
|
entity |
| Predicate | villageNearby |
P98802
|
FINISHED |
| Object | Cape Porpoise |
—
|
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: Cape Porpoise | Statement: [Stage Island, villageNearby, Cape Porpoise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: villageNearby Context triple: [Stage Island, villageNearby, Cape Porpoise]
-
A.
nearbySettlements
Indicates that one settlement is located close to another settlement in geographic space.
-
B.
hasNearbyTraditionalVillage
Indicates that an entity is located close to or in the vicinity of a traditional village.
-
C.
nearbySettlementRegion
Indicates that a settlement is located close to or within the surrounding area of a specified region.
-
D.
nearbyIndianTown
Indicates that one location is a town in India situated close to the referenced place.
-
E.
nearbySettlementUS
chosen
Indicates that one settlement is geographically close to another settlement within the United States.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 29, 2026, 8:51 p.m.