Triple
T32623241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bremen transatlantic flight |
E833985
|
entity |
| Predicate | countryOfAircraftRegistration |
P7983
|
FINISHED |
| Object | Germany |
—
|
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: Germany | Statement: [Bremen transatlantic flight, countryOfAircraftRegistration, Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryOfAircraftRegistration Context triple: [Bremen transatlantic flight, countryOfAircraftRegistration, Germany]
-
A.
operatesAircraftRegistrationCountry
Indicates that an entity operates or uses an aircraft that is registered in a specified country.
-
B.
aircraftOriginCountry
Indicates the country from which an aircraft originates, such as where it was built, registered, or primarily associated.
-
C.
countryOfRegistry
chosen
Indicates the country in which an entity (such as a ship, aircraft, or company) is officially registered.
-
D.
aircraftRegistration
Indicates that an aircraft is assigned a specific official registration identifier or code.
-
E.
airportLocationCountry
Indicates that an airport is geographically situated within a specific country.
- 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_69f3492ccc80819086ef7d26e9786647 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a006417d1f4819093b2da02dbf2ab22 |
completed | May 10, 2026, 10:55 a.m. |
| PD | Predicate disambiguation | batch_6a00634a7a748190ac4774493fce3d30 |
completed | May 10, 2026, 10:51 a.m. |
Created at: May 1, 2026, 1:06 a.m.