Triple
T34270818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cessna 340 |
E879308
|
entity |
| Predicate | sharesTailWith |
P201527
|
FINISHED |
| Object | Cessna 310 |
—
|
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: Cessna 310 | Statement: [Cessna 340, sharesTailWith, Cessna 310]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesTailWith Context triple: [Cessna 340, sharesTailWith, Cessna 310]
-
A.
sharesBaseWith
Indicates that two entities have a common underlying base element, source, or component from which they are derived or constructed.
-
B.
sharesWith
Indicates that one entity gives another entity access to or use of something it possesses.
-
C.
sharesAlignmentWith
Indicates that two entities have the same or sufficiently similar alignment, orientation, or stance according to a defined alignment system.
-
D.
sharesFieldWith
Indicates that two entities are involved in or associated with the same field, discipline, or area of specialization.
-
E.
sharesStartWith
Indicates that two entities have starting segments or initial portions that are identical or share the same beginning.
- F. None of above. chosen
Provenance (4 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_69f349b4f5fc819094b441d18e95e5f1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a000014497c819088d5cda3977522dd |
completed | May 10, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69ffff9a52b08190be1024e0fb6fe661 |
completed | May 10, 2026, 3:46 a.m. |
| PDg | Predicate description generation | batch_6a000013004c8190a01710441f881fdc |
completed | May 10, 2026, 3:48 a.m. |
Created at: May 1, 2026, 1:56 a.m.