Triple
T1404023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snake Dike |
E31648
|
entity |
| Predicate | recommendedRack |
P16857
|
FINISHED |
| Object | light traditional rack |
—
|
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: light traditional rack | Statement: [Snake Dike, recommendedRack, light traditional rack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recommendedRack Context triple: [Snake Dike, recommendedRack, light traditional rack]
-
A.
commendedFor
Indicates that one entity has expressed praise or approval toward another entity specifically because of a particular action, quality, or achievement.
-
B.
recommendedEquipment
chosen
Indicates that one entity suggests or endorses another entity as suitable equipment to be used in a particular context or activity.
-
C.
implementsRecommendationOf
Indicates that one entity carries out or puts into practice a recommendation that was proposed or issued by another entity.
-
D.
canRecommend
Indicates that one entity is able or authorized to suggest or endorse another entity as suitable or preferable.
-
E.
chamberSupportedBy
Indicates that a chamber is physically held up, carried, or structurally sustained by another object or structure.
- 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3a0330c8190b22452d29c79fcf4 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf030a388190bc82d30b9233e873 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.