Triple
T20059735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argus As 10 |
E499435
|
entity |
| Predicate | notableVariant |
P4680
|
FINISHED |
| Object | Argus As 10C |
—
|
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: Argus As 10C | Statement: [Argus As 10, notableVariant, Argus As 10C]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Argus As 10C Context triple: [Argus As 10, notableVariant, Argus As 10C]
-
A.
Argus As 10
chosen
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
Argus As 014 was a German World War II pulsejet engine best known for powering the V-1 flying bomb.
-
C.
Asen
Asen was a medieval Bulgarian noble and co-leader, with his brother Peter, of the uprising that restored the Second Bulgarian Empire in the late 12th century.
-
D.
The Argus
The Argus was a prominent Melbourne-based newspaper in 19th-century Australia, known for its influence on public opinion and literary culture.
-
E.
Argos
Argos is the common nickname for the Toronto Argonauts, a professional Canadian Football League team based in Toronto.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66374f4a48190beb575a6c84ebdb4 |
completed | April 20, 2026, 5:33 p.m. |
Created at: April 11, 2026, 3:38 p.m.