Triple
T16850216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alphabet Other Bets |
E409654
|
entity |
| Predicate | innovationApproach |
P1484
|
FINISHED |
| Object | moonshot factory model |
—
|
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: moonshot factory model | Statement: [Alphabet Other Bets, innovationApproach, moonshot factory model]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: innovationApproach Context triple: [Alphabet Other Bets, innovationApproach, moonshot factory model]
-
A.
innovationFrom
Indicates that something originates, arises, or is derived as an innovation from a particular source or prior entity.
-
B.
innovation
chosen
Indicates the introduction or development of something new or significantly improved compared to existing methods, products, or ideas.
-
C.
innovationLevel
Indicates the degree or extent to which something is new, original, or creatively advanced compared to existing norms or solutions.
-
D.
innovationArea
Indicates the thematic or domain-specific field in which an innovation is focused or applied.
-
E.
usedInnovation
Indicates that one entity applied or implemented an innovation (such as a new idea, method, or technology) in relation to another entity or context.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b378dda48190ab81d75f2cfe3ab3 |
completed | April 18, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.