Triple
T35701603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harold F. Pitcairn |
E1031599
|
entity |
| Predicate | licensedTechnology |
P184076
|
FINISHED |
| Object | Cierva autogyro patents |
—
|
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: Cierva autogyro patents | Statement: [Harold F. Pitcairn, licensedTechnology, Cierva autogyro patents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: licensedTechnology Context triple: [Harold F. Pitcairn, licensedTechnology, Cierva autogyro patents]
-
A.
licensedTechnologyFrom
chosen
Indicates that one entity has obtained the legal right to use another entity’s technology through a licensing agreement.
-
B.
licensedProductType
Indicates the type or category of product for which a license has been granted.
-
C.
restrictedTechnology
Indicates that the use, access, or transfer of a technology is limited or controlled by rules, policies, or regulations.
-
D.
licenseUsed
Indicates that a particular license has been applied to or is being utilized for a specific resource, activity, or entity.
-
E.
technologyEnabled
Indicates that one entity provides or supports the technological means that allow another entity, process, or capability to function or be carried out.
- 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_69f76e0d393c8190b6303c64408736db |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:05 p.m.