Triple
T9045333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgian supra |
E216740
|
entity |
| Predicate | followsCustom |
P26745
|
FINISHED |
| Object | strict toasting order |
—
|
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: strict toasting order | Statement: [Georgian supra, followsCustom, strict toasting order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsCustom Context triple: [Georgian supra, followsCustom, strict toasting order]
-
A.
follows
Indicates that one entity comes after, moves behind, or acts in accordance with another entity in time, space, or sequence.
-
B.
followsBy
Indicates that one event, state, or entity occurs or comes immediately after another in a sequence or order.
-
C.
followsComponent
Indicates that one component comes after or succeeds another component in a defined sequence or structure.
-
D.
followsWork
Indicates that one work (such as a publication, version, or creative piece) comes directly after another in sequence or succession.
-
E.
followsSystem
chosen
Indicates that one entity adheres to, complies with, or operates according to a particular system, framework, or set of rules defined by 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_69ca83d22d488190adbce5e020e9cd1d |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6b148b188190814d64acae493634 |
completed | April 1, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee566b081909e3cdaf551dbd0ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:09 p.m.