Triple
T2201520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Talavera pottery |
E50498
|
entity |
| Predicate | requiresProcess |
P100
|
FINISHED |
| Object | hand-throwing or molding of clay |
—
|
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: hand-throwing or molding of clay | Statement: [Talavera pottery, requiresProcess, hand-throwing or molding of clay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresProcess Context triple: [Talavera pottery, requiresProcess, hand-throwing or molding of clay]
-
A.
requires
chosen
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
B.
requiresSoftware
Indicates that one entity depends on specific software being present or installed in order to function, operate, or be used.
-
C.
requiresNotificationTo
Indicates that one entity must send a notification to another entity before or when a certain condition, event, or action occurs.
-
D.
requiresDetectionOf
Indicates that one entity can only occur, be valid, or proceed if another entity has first been detected or identified.
-
E.
requiresProofOf
Indicates that one entity must provide formal evidence or documentation to validate or authorize 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_69a88b044ab48190add007487680f009 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbfa1b41c8190b0f7467d0dcdfbcd |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda706f4819094de73e1d1d1f539 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.