Triple
T28019854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M Track |
E707655
|
entity |
| Predicate | usesPowerSystem |
P8164
|
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: [M Track, usesPowerSystem, AC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPowerSystem Context triple: [M Track, usesPowerSystem, AC]
-
A.
poweringSystem
Indicates that one entity serves as the source of power or energy that enables the operation or functioning of another entity.
-
B.
usesPowerFor
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
-
C.
usesElectricityFor
Indicates that one entity relies on or employs electricity as the power source to operate, perform a function, or carry out an activity for another entity or purpose.
-
D.
hasPowerHouse
Indicates that one entity possesses or contains a primary energy-producing or central operational unit (a "power house") associated with it.
-
E.
hasPowerSource
chosen
Indicates that an entity derives its operational energy or functionality from a specified power source.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 27, 2026, 8:09 p.m.