Triple
T29971763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gemini 9 |
E761335
|
entity |
| Predicate | EVAIssues |
P29037
|
FINISHED |
| Object | visor fogging and high workload |
—
|
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: visor fogging and high workload | Statement: [Gemini 9, EVAIssues, visor fogging and high workload]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EVAIssues Context triple: [Gemini 9, EVAIssues, visor fogging and high workload]
-
A.
involvesIssue
chosen
Indicates that an action, event, or entity is related to, concerns, or includes a particular issue.
-
B.
issues
Indicates that an entity formally produces, releases, or distributes something, such as a document, order, or resource, making it officially available.
-
C.
underlyingIssue
Indicates that one situation, problem, or condition is the fundamental cause or root problem behind another.
-
D.
subjectOfConcernFor
Indicates that one entity is regarded as a matter of worry, interest, or attention for another entity.
-
E.
inUniverseIssueAddressed
Indicates that a narrative work explicitly addresses or resolves an issue within its own fictional universe, rather than only implying or ignoring it.
- 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6786ee1608190ad7cf42111f2b7df |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:32 p.m.