Triple
T11328069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leon Wasilewski |
E268274
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Leon |
E79700
|
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: Leon | Statement: [Leon Wasilewski, givenName, Leon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leon Context triple: [Leon Wasilewski, givenName, Leon]
-
A.
Leon
chosen
Leon is a masculine given name of Greek origin meaning "lion," commonly used in various cultures worldwide.
-
B.
Leo
Leo is a 2023 Indian Tamil-language action thriller film directed by Lokesh Kanagaraj and starring Vijay, noted for its high-octane action and connection to the Lokesh Cinematic Universe.
-
C.
Leo
Leo is a masculine given name of Latin origin meaning "lion," historically borne by popes, saints, and rulers.
-
D.
Leo
Leo is a zodiac constellation and astrological sign traditionally associated with the lion, symbolizing courage, leadership, and creativity.
-
E.
Leo
Leo was the given name of Leo V of Armenia, the last king of the Armenian Kingdom of Cilicia in the late 14th century.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9e330008190b75490efde01dc59 |
completed | April 9, 2026, 6:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e52608b7348190875597513ca1a995 |
completed | April 19, 2026, 6:59 p.m. |
Created at: April 8, 2026, 9:32 p.m.