Triple
T322413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TMS |
E6441
|
entity |
| Predicate | sampledOn |
P6024
|
FINISHED |
| Object | TCK rising edge |
—
|
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: TCK rising edge | Statement: [TMS, sampledOn, TCK rising edge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sampledOn Context triple: [TMS, sampledOn, TCK rising edge]
-
A.
commissionedAt
Indicates the time or date at which something (such as a work, project, or task) was formally commissioned or initiated.
-
B.
measuredAt
chosen
Indicates the time or point at which a measurement was taken or recorded for an entity or event.
-
C.
displayedAt
Indicates that one entity is presented or exhibited at a particular location, venue, or event.
-
D.
capturedDuring
Indicates that one event or state occurred within the temporal span of another, typically representing that something was recorded, seized, or documented while a specific situation or activity was taking place.
-
E.
observedSince
Indicates that one entity has been continuously or repeatedly observed starting from a specified point in time.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea81a1e88190b3496070eb3d85f5 |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e948048c819098ba4de9261ef2ef |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.