Triple
T20709269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L’Entreprenant |
E508988
|
entity |
| Predicate | innovationStatus |
P94439
|
FINISHED |
| Object | pioneering military use of aerostats |
—
|
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: pioneering military use of aerostats | Statement: [L’Entreprenant, innovationStatus, pioneering military use of aerostats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: innovationStatus Context triple: [L’Entreprenant, innovationStatus, pioneering military use of aerostats]
-
A.
innovationLevel
Indicates the degree or extent to which something is new, original, or creatively advanced compared to existing norms or solutions.
-
B.
hasInnovationType
chosen
Indicates that an entity is associated with, or classified by, a specific type or category of innovation.
-
C.
innovationFrom
Indicates that something originates, arises, or is derived as an innovation from a particular source or prior entity.
-
D.
innovationArea
Indicates the thematic or domain-specific field in which an innovation is focused or applied.
-
E.
innovation
Indicates the introduction or development of something new or significantly improved compared to existing methods, products, or ideas.
- 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1961090819090daf7254f90a176 |
completed | April 21, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:14 p.m.