Triple
T10977322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlie Brent |
E259404
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Charlie |
E473877
|
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: Charlie | Statement: [Charlie Brent, givenName, Charlie]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Charlie Context triple: [Charlie Brent, givenName, Charlie]
-
A.
Charlie
Charlie is Dory’s loving but forgetful father in the animated film "Finding Dory," known for his patience, optimism, and inventive ways of helping her cope with memory loss.
-
B.
Charlie
chosen
Charlie is the given name of the British philosopher and Cambridge academic C. D. Broad.
-
C.
Charlie
Charlie is the yellow-suited captain and one of the three main playable leaders in Pikmin 3, known for commanding Pikmin on the planet PNF-404.
-
D.
Charlie
Charlie is a central character in the romantic comedy film "French Kiss," serving as the unfaithful fiancé whose actions set the story’s events in motion.
-
E.
Charlie
Charlie is a character featured in the work titled "Seascape."
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d771f6a9448190b3932ee801ae0da9 |
completed | April 9, 2026, 9:31 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e374526d54819085a0fb0d62f7a581 |
completed | April 18, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:24 p.m.