Triple
T9071452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ETC |
E217374
|
entity |
| Predicate | canTrack |
P54613
|
FINISHED |
| Object | gold |
—
|
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: gold | Statement: [ETC, canTrack, gold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canTrack Context triple: [ETC, canTrack, gold]
-
A.
isTrackedBy
Indicates that an entity’s state, behavior, or changes are being monitored, recorded, or followed by another entity.
-
B.
usesTrackage
Indicates that one transportation operator or service runs its vehicles over railway or transit tracks that are owned or controlled by another entity.
-
C.
trackAccess
Indicates that one entity monitors, records, or keeps a log of another entity’s access or usage of a resource.
-
D.
trackingAvailable
chosen
Indicates that tracking information or functionality is available for the associated item, process, or interaction.
-
E.
isTrackEvent
Indicates that an event is classified as a track-related occurrence, such as a specific action or interaction being recorded for tracking or analytics purposes.
- 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_69ca83d6c14c8190bc056d927f00a2a2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc955ec5c0819089bb42448edf391e |
completed | April 1, 2026, 3:47 a.m. |
| PD | Predicate disambiguation | batch_69cc65f881248190bfd220bb28a9fb5f |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:12 p.m.