Triple
T10417815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aster 15 |
E245565
|
entity |
| Predicate | designer |
P184
|
FINISHED |
| Object | Eurosam |
E809141
|
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: Eurosam | Statement: [Aster 15, designer, Eurosam]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eurosam Context triple: [Aster 15, designer, Eurosam]
-
A.
Eurosam
chosen
Eurosam is a European defense consortium specializing in the design and production of advanced surface-to-air missile systems.
-
B.
Euromos
Euromos was an ancient Greek city in the region of Caria in southwestern Asia Minor, noted especially for its well-preserved Temple of Zeus.
-
C.
Europa Reach
Europa Reach is a specific waterway or passage within the Douglas Channel system, likely serving as one of its navigable reaches along the British Columbia coast.
-
D.
Simoa
Simoa is a river in southeastern Norway that flows through Buskerud county before joining the larger Drammenselva river system.
-
E.
Mosina
Mosina is an alternative name for Vurës, a language spoken on the island of Vanua Lava in Vanuatu.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea1194e08190a18c3b3002147493 |
completed | April 7, 2026, 11:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d87e9b86648190b83eb5261c9a7b97 |
completed | April 10, 2026, 4:37 a.m. |
Created at: April 6, 2026, 12:11 p.m.