Triple
T18242621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VD |
E436855
|
entity |
| Predicate | followedByOnPlate |
P130993
|
FINISHED |
| Object | serial number |
—
|
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: serial number | Statement: [VD, followedByOnPlate, serial number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedByOnPlate Context triple: [VD, followedByOnPlate, serial number]
-
A.
followedByComponent
Indicates that one component directly succeeds another component in a defined sequence or order.
-
B.
followedByTitle
Indicates that one title directly succeeds another in a sequence or ordered list.
-
C.
followedByOnSite
Indicates that one event, action, or entity occurs immediately after another at the same physical location or site.
-
D.
followsBy
Indicates that one event, state, or entity occurs or comes immediately after another in a sequence or order.
-
E.
followedByInProductionOrder
Indicates that one process, step, or item directly succeeds another in a defined production sequence or workflow order.
- 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_69d8b91104e08190a8241f7d260a5162 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f7e4f0548190bc617e6acd17010d |
completed | April 19, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:33 a.m.