Triple
T15316513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amandus Adamson |
E366172
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Amandus |
E807877
|
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: Amandus | Statement: [Amandus Adamson, givenName, Amandus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Amandus Context triple: [Amandus Adamson, givenName, Amandus]
-
A.
Amandus
chosen
Amandus is a masculine given name of Latin origin, historically used in various European countries and related to the name Amanda.
-
B.
Armandus
Armandus is a masculine given name, a Latinized variant of Armand, historically associated with European, particularly French and Dutch, usage.
-
C.
Amelius
Amelius was a 3rd-century Neoplatonist philosopher and disciple of Plotinus, known for his extensive commentaries on Platonic thought.
-
D.
Thaddaeus
Thaddaeus is a disciple of Jesus traditionally counted among the Twelve Apostles in Christian tradition, often identified with Jude the Apostle.
-
E.
Reimund
Reimund is a masculine given name, primarily used in German-speaking regions, that is a variant of the name Raymond.
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03dd1d384819098f38402a8740d91 |
completed | April 16, 2026, 1:39 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fef8a688a48190848eb7f065aba146 |
completed | May 9, 2026, 9:04 a.m. |
Created at: April 10, 2026, 3:16 a.m.