Triple
T33682010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rewrite |
E862925
|
entity |
| Predicate | trackBy |
P180468
|
FINISHED |
| Object | Paul Simon |
—
|
NE NERFINISHED |
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: Paul Simon | Statement: [Rewrite, trackBy, Paul Simon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackBy Context triple: [Rewrite, trackBy, Paul Simon]
-
A.
trackFrom
Indicates a source or origin from which something is tracked or monitored.
-
B.
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.
-
C.
trackOver
Indicates that one entity follows, monitors, or records the behavior, state, or progress of another entity across a period of time or over a sequence of events.
-
D.
trackFeature
Indicates that one entity monitors, records, or follows the behavior, state, or evolution of a particular feature associated with another entity.
-
E.
trackedOn
Indicates that the subject’s status, activity, or changes are being monitored or recorded on the specified system, platform, or medium.
- 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_69f3498662b48190904442c39df84fb7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
| PDg | Predicate description generation | batch_69f74061c440819080434155c2d60341 |
completed | May 3, 2026, 12:32 p.m. |
Created at: May 1, 2026, 1:43 a.m.