Triple
T29132587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Why Not Sneeze, Rrose Sélavy? |
E738418
|
entity |
| Predicate | hasWeightCharacteristic |
P70576
|
FINISHED |
| Object | unexpected heaviness due to marble |
—
|
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: unexpected heaviness due to marble | Statement: [Why Not Sneeze, Rrose Sélavy?, hasWeightCharacteristic, unexpected heaviness due to marble]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWeightCharacteristic Context triple: [Why Not Sneeze, Rrose Sélavy?, hasWeightCharacteristic, unexpected heaviness due to marble]
-
A.
وزن
chosen
Indicates a relationship where one entity has, measures, or is characterized by a certain weight or mass.
-
B.
weightCondition
Indicates that a specified weight-related requirement or constraint holds between entities or values.
-
C.
emptyWeight
Indicates the weight of an object or vehicle when it is empty, excluding any load, cargo, or passengers.
-
D.
intendedWeight
Indicates the target or desired weight that an entity is meant or planned to have, rather than its current actual weight.
-
E.
weight
Indicates a relationship where a numerical value quantifies how heavy an entity is, often used to measure or compare mass or load.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 11:32 a.m.