Triple
T38401732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schweizer 333 |
E900915
|
entity |
| Predicate | manufacturerLaterOwner |
P144443
|
FINISHED |
| Object | Sikorsky Aircraft |
—
|
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: Sikorsky Aircraft | Statement: [Schweizer 333, manufacturerLaterOwner, Sikorsky Aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: manufacturerLaterOwner Context triple: [Schweizer 333, manufacturerLaterOwner, Sikorsky Aircraft]
-
A.
formerManufacturer
Indicates that an entity previously manufactured another entity but no longer does so.
-
B.
previouslyPossessedBy
Indicates that an entity was owned or possessed by another entity at some time in the past, but is not necessarily possessed by that entity now.
-
C.
ownerOrManufacturer
Indicates that the related entity either owns the item or is the entity that manufactured it.
-
D.
ownerLater
chosen
Indicates that one entity becomes the owner of another entity at a later point in time, after some prior state or ownership.
-
E.
successorManufacturer
Indicates that one manufacturer has taken over, replaced, or continued the role or operations of another manufacturer as its successor.
- 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.