Triple
T14782021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LZ 130 Graf Zeppelin II |
E347412
|
entity |
| Predicate | reasonForHydrogenUse |
P101297
|
FINISHED |
| Object | U.S. export ban on helium |
—
|
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: U.S. export ban on helium | Statement: [LZ 130 Graf Zeppelin II, reasonForHydrogenUse, U.S. export ban on helium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForHydrogenUse Context triple: [LZ 130 Graf Zeppelin II, reasonForHydrogenUse, U.S. export ban on helium]
-
A.
reasonForUse
Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
-
B.
fuelChoiceRationale
chosen
Indicates the reasoning or justification behind selecting a particular type of fuel over alternatives.
-
C.
reservoirUse
Indicates the way a reservoir is utilized or the purpose for which its stored water is used.
-
D.
hasWaterUse
Indicates a relationship where one entity utilizes or consumes water for a particular purpose, process, or function.
-
E.
waterUse
Indicates the amount or manner in which water is consumed, utilized, or withdrawn by an entity or activity.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deca9de3f48190b7706925e2947cf5 |
completed | April 14, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69de8c090d1081909b5a9bf437499d6c |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.