Triple
T15632974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EC |
E375865
|
entity |
| Predicate | hasSubdivision |
P747
|
FINISHED |
| Object | EC2 |
E974441
|
NE FINISHED |
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: EC2 | Statement: [EC, hasSubdivision, EC2]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EC2 Context triple: [EC, hasSubdivision, EC2]
-
A.
Amazon EC2
chosen
Amazon EC2 is a scalable cloud computing service that provides virtual servers (instances) for running applications on Amazon Web Services infrastructure.
-
B.
EC2M
EC2M is a central London postcode sector covering part of the City of London around Liverpool Street and its surrounding commercial and financial areas.
-
C.
EC2V
EC2V is a central London postcode district covering part of the City of London’s financial and commercial core.
-
D.
ECS
ECS is Amazon's fully managed container orchestration service that runs and scales Docker containers on AWS infrastructure.
-
E.
ECS
ECS (Enhanced Chip Set) is an improved version of the Amiga computer’s original graphics and system chipset, offering expanded display modes and hardware capabilities over its predecessor.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04eb7338881909f3c430bb73f91d1 |
completed | April 16, 2026, 2:51 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff5f472b648190b7cd532a1b16373e |
completed | May 9, 2026, 4:22 p.m. |
Created at: April 10, 2026, 4:14 a.m.