Triple
T12393341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tizard Mission |
E296051
|
entity |
| Predicate | sharesTechnology |
P54349
|
FINISHED |
| Object | cavity magnetron |
—
|
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: cavity magnetron | Statement: [Tizard Mission, sharesTechnology, cavity magnetron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesTechnology Context triple: [Tizard Mission, sharesTechnology, cavity magnetron]
-
A.
sharesTechnologyWith
chosen
Indicates that one entity provides, exchanges, or jointly uses technology with another entity.
-
B.
sharesInnovationWith
Indicates that one entity shares or exchanges innovative ideas, methods, or technologies with another entity.
-
C.
sharesPlatformWith
Indicates that two entities operate on, are available through, or participate within the same platform or system.
-
D.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
E.
share
Indicates that one entity gives, divides, or jointly uses a resource, item, or information with another entity.
- 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_69d6ad9e653c8190b1473c860ee53dae |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e1888b48190bd750f839a26e99e |
completed | April 10, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69d94d354b488190adc83fb4f2770dd5 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:54 p.m.