Triple
T38189385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cedar Island, North Carolina |
E1005409
|
entity |
| Predicate | ferryOperatedBy |
P5933
|
FINISHED |
| Object | North Carolina Ferry System |
—
|
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: North Carolina Ferry System | Statement: [Cedar Island, North Carolina, ferryOperatedBy, North Carolina Ferry System]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ferryOperatedBy Context triple: [Cedar Island, North Carolina, ferryOperatedBy, North Carolina Ferry System]
-
A.
ferryOperator
chosen
Indicates that one entity operates, manages, or runs a ferry service for another entity or in a particular context.
-
B.
ferryOperatorType
Indicates the type or category of operator responsible for running a ferry service.
-
C.
ferryFlightCarrier
Indicates that one carrier operates a ferry (non-revenue repositioning) flight on behalf of another carrier.
-
D.
ferryNetworkBrand
Indicates the brand or commercial identity under which a ferry network operates or is marketed.
-
E.
ferryServiceName
Indicates the specific name assigned to a ferry service operating between locations.
- 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_69f76dbd22f48190940318cea061e8bb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:29 p.m.