Triple
T25593191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunder Stone |
E641576
|
entity |
| Predicate | weightAfterCarving |
P70576
|
FINISHED |
| Object | about 1250 tonnes |
—
|
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: about 1250 tonnes | Statement: [Thunder Stone, weightAfterCarving, about 1250 tonnes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weightAfterCarving Context triple: [Thunder Stone, weightAfterCarving, about 1250 tonnes]
-
A.
weightAfterRecut
Indicates the resulting weight of an item or material after it has been cut, trimmed, or recut from its original form.
-
B.
intendedWeight
Indicates the target or desired weight that an entity is meant or planned to have, rather than its current actual weight.
-
C.
وزن
chosen
Indicates a relationship where one entity has, measures, or is characterized by a certain weight or mass.
-
D.
hasCarving
Indicates that one entity features or contains a carved design, inscription, or sculpted detail that is associated with or applied to another entity.
-
E.
dryMass
Indicates the mass of an object excluding any contained fluids, propellants, or other consumable materials.
- 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 4:25 p.m.