Triple
T1990531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Percy Bysshe Shelley |
E43241
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Percy |
E172159
|
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: Percy | Statement: [Percy Bysshe Shelley, givenName, Percy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Percy Context triple: [Percy Bysshe Shelley, givenName, Percy]
-
A.
Percy
chosen
Percy is a masculine given name of Old French origin, famously borne by American physicist and Nobel laureate Percy W. Bridgman.
-
B.
Jackson-Perseus
Jackson-Perseus is a publishing imprint under the Perseus Books Group, known for releasing a range of nonfiction and trade titles.
-
C.
Luke
Luke is traditionally regarded as the author of the Gospel of Luke and the Acts of the Apostles in the New Testament, and is thought to have been a physician and companion of the Apostle Paul.
-
D.
Perseus
Perseus is a legendary Greek hero famed for slaying the Gorgon Medusa and rescuing Andromeda.
-
E.
Timoteus
Timoteus is a male given name, commonly used in various European languages and derived from the biblical name Timothy.
- 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_69a88714cf2c819081644be450b8356e |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8451fe8819093531052f4533c36 |
completed | March 7, 2026, 5:31 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae0338631c8190a8c7e5177ac473a8 |
completed | March 8, 2026, 11:16 p.m. |
Created at: March 4, 2026, 7:37 p.m.