Triple
T35537670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Britain electricity distribution system |
E1026973
|
entity |
| Predicate | usesCurrentType |
P8870
|
FINISHED |
| Object | AC |
—
|
LITERAL 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: AC | Statement: [Great Britain electricity distribution system, usesCurrentType, AC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCurrentType Context triple: [Great Britain electricity distribution system, usesCurrentType, AC]
-
A.
usesCurrentObject
Indicates that an entity makes use of, interacts with, or operates on the currently referenced object in a given context.
-
B.
hasCurrentType
chosen
Indicates that an entity currently possesses or is classified under a specific type or category, as opposed to past or potential types.
-
C.
usedWithType
Indicates that something is typically or appropriately used together with items of a specified type.
-
D.
usedInType
Indicates that something serves as a component, element, or example within a particular type or category.
-
E.
usesStandardType
Indicates that one entity employs or relies on a predefined, commonly accepted standard type defined elsewhere.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: May 3, 2026, 4:04 p.m.