Triple
T27799395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spooling Directory Source |
E702196
|
entity |
| Predicate | tracksStateIn |
P1291
|
FINISHED |
| Object | tracker directory |
—
|
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: tracker directory | Statement: [Spooling Directory Source, tracksStateIn, tracker directory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tracksStateIn Context triple: [Spooling Directory Source, tracksStateIn, tracker directory]
-
A.
trackedOn
Indicates that the subject’s status, activity, or changes are being monitored or recorded on the specified system, platform, or medium.
-
B.
tracks
chosen
Indicates that one entity monitors, follows, or keeps a record of another entity’s state, behavior, or progress over time.
-
C.
track
Indicates that one entity follows, monitors, or keeps a record of another entity’s state, behavior, or progress over time.
-
D.
trackOn
Indicates that one entity is physically positioned or moving along the surface or path of another, like a vehicle on a track or rails.
-
E.
usesTrackage
Indicates that one transportation operator or service runs its vehicles over railway or transit tracks that are owned or controlled by another entity.
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 5:33 p.m.