Triple
T26281631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulfstream G800 |
E660712
|
entity |
| Predicate | designShares |
P69276
|
FINISHED |
| Object | G700 fuselage cross-section |
—
|
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: G700 fuselage cross-section | Statement: [Gulfstream G800, designShares, G700 fuselage cross-section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designShares Context triple: [Gulfstream G800, designShares, G700 fuselage cross-section]
-
A.
sharesDesignFeaturesWith
chosen
Indicates that two entities have similar or overlapping design characteristics, structures, or stylistic elements.
-
B.
sharesArchitect
Indicates that two entities have the same architect responsible for their design.
-
C.
designCollaboration
Indicates a collaborative relationship in which two or more entities jointly participate in the design process or co-create a design outcome.
-
D.
sharesIn
Indicates that one entity holds or possesses shares or ownership stakes in another entity.
-
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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 26, 2026, 10:01 p.m.