Triple
T36957971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armadillo Aerospace |
E914235
|
entity |
| Predicate | reasonForHibernation |
P111913
|
FINISHED |
| Object | lack of funding |
—
|
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: lack of funding | Statement: [Armadillo Aerospace, reasonForHibernation, lack of funding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForHibernation Context triple: [Armadillo Aerospace, reasonForHibernation, lack of funding]
-
A.
hibernatesDuring
Indicates that an entity enters a state of hibernation throughout a specified time period or season.
-
B.
hiatusReason
chosen
Indicates the reason or cause for a pause, break, or interruption in an ongoing activity or process.
-
C.
suspensionReason
Indicates the reason or cause for which an entity has been suspended from a status, activity, or service.
-
D.
hibernationStart
Indicates the time or event at which an organism begins its hibernation period.
-
E.
reasonForSuppression
Indicates the justification or cause for which something (such as information, data, or content) has been withheld, hidden, or prevented from being shown or used.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
Created at: May 3, 2026, 4:13 p.m.