Triple
T30502240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exchange Traded Commodity |
E776166
|
entity |
| Predicate | mayTrack |
P169794
|
FINISHED |
| Object | single commodity |
—
|
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: single commodity | Statement: [Exchange Traded Commodity, mayTrack, single commodity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayTrack Context triple: [Exchange Traded Commodity, mayTrack, single commodity]
-
A.
trackedOn
Indicates that the subject’s status, activity, or changes are being monitored or recorded on the specified system, platform, or medium.
-
B.
isTrackedBy
Indicates that an entity’s state, behavior, or changes are being monitored, recorded, or followed by another entity.
-
C.
usesTrackage
Indicates that one transportation operator or service runs its vehicles over railway or transit tracks that are owned or controlled by another entity.
-
D.
trackAccess
Indicates that one entity monitors, records, or keeps a log of another entity’s access or usage of a resource.
-
E.
isTracked
Indicates that an entity’s state, behavior, or presence is being monitored or recorded over time.
- F. None of above. chosen
Provenance (4 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f687812a6481908b126c0aacd38936 |
completed | May 2, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f6827a7b9c8190ab13605aacc81df9 |
completed | May 2, 2026, 11:02 p.m. |
Created at: April 29, 2026, 8:15 p.m.