Triple
T26130360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bristol Jupiter |
E659227
|
entity |
| Predicate | licenseProductionIn |
P45762
|
FINISHED |
| Object | Poland |
—
|
NE NERFINISHED |
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: Poland | Statement: [Bristol Jupiter, licenseProductionIn, Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: licenseProductionIn Context triple: [Bristol Jupiter, licenseProductionIn, Poland]
-
A.
licenseProduction
chosen
Indicates that one party is authorized to manufacture or produce something under a license granted by another party.
-
B.
licenseFor
Indicates that one entity grants or holds formal permission or authorization for another entity to perform an activity, use a resource, or operate under specified conditions.
-
C.
licensePublisher
Indicates that an entity is the organization or agent responsible for issuing or publishing a particular license.
-
D.
licenseFocus
Indicates that a license specifically targets, applies to, or is primarily concerned with a particular subject, activity, or scope.
-
E.
licenseBuiltIn
Indicates that a license is inherently included within or comes standard as part of another product, service, or system rather than being added separately.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60b9202b08190b2dca041b547d64e |
completed | May 2, 2026, 2:34 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 8:14 p.m.