Triple
T12010538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argus As 014 |
E285891
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Argus As 14 |
E324070
|
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: Argus As 14 | Statement: [Argus As 014, alsoKnownAs, Argus As 14]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Argus As 14 Context triple: [Argus As 014, alsoKnownAs, Argus As 14]
-
A.
Argus As 10
The Argus As 10 is a German air-cooled inverted V8 aircraft engine widely used in light aircraft and trainers during the 1930s and World War II.
-
B.
Argus As 014
chosen
Argus As 014 was a German World War II pulsejet engine best known for powering the V-1 flying bomb.
-
C.
Argus
Argus is a many-eyed giant from Greek mythology best known for his role as a vigilant guardian.
-
D.
Argus
Argus is an early distributed programming language known for pioneering concepts in fault-tolerant, distributed systems and influencing modern object-oriented and concurrent programming.
-
E.
Argos
Argos is a major UK-based catalogue and online retailer known for offering a wide range of household goods, electronics, toys, and more through both physical stores and digital channels.
- 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903d7777481908cd5a001f75e2ee3 |
completed | April 10, 2026, 2:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f48b363c6481908c8414c1eecc14f5 |
completed | May 1, 2026, 11:15 a.m. |
Created at: April 8, 2026, 9:46 p.m.