Triple
T38633631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W-53 |
E937521
|
entity |
| Predicate | hasYieldClass |
P128568
|
FINISHED |
| Object | megaton-range |
—
|
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: megaton-range | Statement: [W-53, hasYieldClass, megaton-range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasYieldClass Context triple: [W-53, hasYieldClass, megaton-range]
-
A.
hasYield
Indicates that one entity produces, returns, or generates a measurable output, result, or profit for another entity or context.
-
B.
maximumYieldClass
chosen
Indicates the highest yield category or class that can be assigned to or achieved by an entity within a defined yield classification system.
-
C.
hasOutcomeClass
Indicates that something is associated with a particular category or type of outcome.
-
D.
requiresLowerMaximumYields
Indicates that one entity imposes a constraint on another such that the allowed or achievable maximum yields must be reduced.
-
E.
yieldClassification
Indicates how an outcome, result, or production level is categorized or labeled according to predefined yield criteria.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.