Triple
T13353042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gemini 2 |
E318115
|
entity |
| Predicate | reusedHardware |
P91997
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Gemini 2, reusedHardware, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reusedHardware Context triple: [Gemini 2, reusedHardware, yes]
-
A.
reusedIn
chosen
Indicates that something previously used in one context or instance is used again in another context or instance.
-
B.
partiallyReusedAs
Indicates that one entity is used again as part of another entity, but only to a limited or incomplete extent rather than in its entirety.
-
C.
infrastructureReuse
Indicates that existing infrastructure is being used again for a new or continued purpose instead of building or deploying entirely new infrastructure.
-
D.
materialReusedAt
Indicates that some or all of a material is used again at a specified location or facility.
-
E.
refurbishedIn
Indicates that an entity has undergone restoration, repair, or renovation at a specific time or during a particular period.
- 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99e8d520881908aa23c7102b72b72 |
completed | April 11, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69d98f6fd8bc819086dddb6f376efa57 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:32 p.m.