Triple
T96468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carl Gustaf Emil Mannerheim |
E1942
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Carl |
E2910
|
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: Carl | Statement: [Carl Gustaf Emil Mannerheim, givenName, Carl]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Carl Context triple: [Carl Gustaf Emil Mannerheim, givenName, Carl]
-
A.
Carl
chosen
Carl is the given name of Carl Sagan, the renowned American astronomer, science communicator, and author.
-
B.
Harold
Harold is a masculine given name of Old English origin, historically borne by several notable figures including kings and modern public personalities.
-
C.
Jack
Jack is a common masculine given name, often used as a familiar form of John and widely featured in English-language literature and popular culture.
-
D.
Earl
An Earl is a noble rank in the British and some European peerage systems, historically positioned below a marquess and above a viscount.
-
E.
Edwin
Edwin is a masculine given name of Old English origin meaning "rich friend" or "prosperous friend."
- 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_69a24d4862f881908cc8b89d3a78031d |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a24fd5cecc8190aca5fb4c4fe91a19 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a34418bb848190ac26adef7f990f93 |
completed | Feb. 28, 2026, 7:38 p.m. |
Created at: Feb. 28, 2026, 2:09 a.m.