Triple
T32440826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Henry |
E829009
|
entity |
| Predicate | formsEntranceWith |
P185337
|
FINISHED |
| Object | Cape Charles |
—
|
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 Charles | Statement: [Cape Henry, formsEntranceWith, Cape Charles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsEntranceWith Context triple: [Cape Henry, formsEntranceWith, Cape Charles]
-
A.
formationEntered
Indicates that an entity has moved into and assumed a specified formation relative to other entities.
-
B.
entersFrom
Indicates that one entity moves into or arrives at a place, state, or context by coming from another specified source or location.
-
C.
entersBy
Indicates that one entity moves into or gains access to another entity through a specified entrance, route, or means.
-
D.
entranceTrait
Indicates a characteristic or feature associated with how an entity enters or is accessed (e.g., through a particular type or style of entrance).
-
E.
enterAs
Indicates that one entity goes into or joins another context, place, or role in the capacity or form specified.
- 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be520f148190ba200bf3dbf40656 |
completed | May 3, 2026, 9:29 p.m. |
Created at: May 1, 2026, 12:55 a.m.