Triple
T14738851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mirage IIIS |
E346287
|
entity |
| Predicate | modifiedBy |
P1121
|
FINISHED |
| Object | F+W Emmen |
E1117665
|
NE 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: F+W Emmen | Statement: [Mirage IIIS, modifiedBy, F+W Emmen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: F+W Emmen Context triple: [Mirage IIIS, modifiedBy, F+W Emmen]
-
A.
F+W Emmen
chosen
F+W Emmen was a Swiss aircraft manufacturer and maintenance company known for producing and servicing military aircraft under license.
-
B.
Buitenhof
Buitenhof is a residential neighborhood located in the Dutch municipality of Leiderdorp in South Holland.
-
C.
Wanneperveen
Wanneperveen is a rural village in the Dutch province of Overijssel, known for its lakes, peat landscapes, and water-based recreation.
-
D.
Volkspark Enschede
Volkspark Enschede is a historic public park in the Dutch city of Enschede, known for its green spaces, walking paths, and recreational facilities.
-
E.
Middenbeemster
Middenbeemster is a historic village in North Holland, Netherlands, known as part of the Beemster polder UNESCO World Heritage landscape.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec73264848190be23c5f0260cbe13 |
completed | April 14, 2026, 11:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe0ce6514c8190a37b023dcc0c1b1a |
completed | May 8, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:29 a.m.