Triple
T110474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | puddling process |
E2236
|
entity |
| Predicate | followedByStep |
P4107
|
FINISHED |
| Object | shingling |
—
|
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: shingling | Statement: [puddling process, followedByStep, shingling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedByStep Context triple: [puddling process, followedByStep, shingling]
-
A.
followsStage
chosen
Indicates that one stage occurs after and in sequence with another stage in a process or workflow.
-
B.
followsRouteOf
Indicates that one entity travels along the same path or route that another entity takes or has taken.
-
C.
follows
Indicates that one entity comes after, moves behind, or acts in accordance with another entity in time, space, or sequence.
-
D.
subsequentOrder
Indicates that one order occurs after or follows another order in sequence.
-
E.
successorInCommand
Indicates that one entity is designated to assume command authority immediately after another entity, typically when the latter is unavailable or their term ends.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a258b58efc8190959c86f73d67b744 |
completed | Feb. 28, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69a25641058c8190b5b64509b35d8176 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.