Triple
T19388307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purmerend |
E484991
|
entity |
| Predicate | publicTransportOperator |
P14541
|
FINISHED |
| Object | EBS |
—
|
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: EBS | Statement: [Purmerend, publicTransportOperator, EBS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EBS Context triple: [Purmerend, publicTransportOperator, EBS]
-
A.
EBS
chosen
EBS is a Dutch public transport company that operates bus services in and around Amsterdam and other regions in the Netherlands.
-
B.
EBS
EBS is a German vehicle registration code assigned to the Bayreuth district in the state of Bavaria.
-
C.
Amazon EBS
Amazon EBS is a scalable, high-performance block storage service used with Amazon EC2 instances for persistent data storage in the AWS cloud.
-
D.
Amazon EFS
Amazon EFS is a fully managed, scalable, cloud-native file storage service that provides shared, elastic file systems for use with AWS compute resources.
-
E.
ECS
ECS is Amazon's fully managed container orchestration service that runs and scales Docker containers on AWS infrastructure.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61b425e848190ab5ae8ae0a034fe2 |
completed | April 20, 2026, 12:25 p.m. |
Created at: April 10, 2026, 1:36 p.m.