Triple
T5754665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CANT |
E126935
|
entity |
| Predicate | designSpecialization |
P62830
|
FINISHED |
| Object | seaplane design |
—
|
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: seaplane design | Statement: [CANT, designSpecialization, seaplane design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designSpecialization Context triple: [CANT, designSpecialization, seaplane design]
-
A.
creatorSpecialization
Indicates the specific field, discipline, or area of expertise in which a creator primarily works or is specialized.
-
B.
designDiscipline
chosen
Indicates a relationship where an entity is associated with, categorized under, or practices a particular field or branch of design.
-
C.
styleSpecialty
Indicates a relationship where an entity’s expertise, focus, or specialization is in a particular style or stylistic approach.
-
D.
designLead
Indicates that one entity serves as the primary designer or person in charge of leading the design work for another entity or project.
-
E.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for 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_69c00832aedc81909899801b141fa3b4 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02904dcf481909e4340a64ee1034e |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021cc68648190bb86d049ebe80f12 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:49 p.m.