Triple
T15393813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gleipnir |
E368116
|
entity |
| Predicate | thicknessComparedTo |
P103295
|
FINISHED |
| Object | silkRibbon |
—
|
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: silkRibbon | Statement: [Gleipnir, thicknessComparedTo, silkRibbon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thicknessComparedTo Context triple: [Gleipnir, thicknessComparedTo, silkRibbon]
-
A.
thickness
Indicates the measure of how deep or wide an object or layer is from one surface or side to its opposite.
-
B.
bodyThickness
chosen
Indicates the measured or relative thickness of an entity’s body in the context of a comparison or description.
-
C.
densityComparedTo
Indicates a comparison between the densities of two entities, specifying which is denser or how their densities relate.
-
D.
scaleComparison
Indicates a relationship where two or more entities are compared in terms of their size, magnitude, or scale relative to one another.
-
E.
isThickenedWith
Indicates that one substance has been made more viscous or dense by adding another substance that serves as a thickening agent.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e7838b48190862b43c6c8620692 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.