Triple
T7599367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Maxwell |
E179942
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Maxwell |
E372700
|
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: Maxwell | Statement: [James Maxwell, familyName, Maxwell]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Maxwell Context triple: [James Maxwell, familyName, Maxwell]
-
A.
Maxwell
Maxwell is the given first name of the influential American jazz drummer and composer Max Roach.
-
B.
Maxwell
Maxwell was an early 20th-century American automobile brand known for producing affordable, mass-market cars before eventually becoming part of Chrysler.
-
C.
Maxwell
Maxwell is the given first name of Lord Beaverbrook, a prominent 20th-century British-Canadian newspaper magnate and politician.
-
D.
Maxwell
Maxwell is the middle name of William M. Evarts, a prominent 19th-century American lawyer, statesman, and U.S. Secretary of State.
-
E.
Maxwell
chosen
Maxwell is a common English surname of Scottish and English origin, borne by numerous notable individuals across various fields.
- 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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9d7cb288190b40ff5c9a09297d9 |
completed | March 27, 2026, 9:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c861ad08bc8190b3fc22109579a47d |
completed | March 28, 2026, 11:18 p.m. |
Created at: March 27, 2026, 3:53 p.m.