Triple
T14305525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William C. Maxwell |
E354683
|
entity |
| Predicate | reasonForNamesake |
P7885
|
FINISHED |
| Object | distinguished military service as an aviator |
—
|
LITERAL 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: distinguished military service as an aviator | Statement: [William C. Maxwell, reasonForNamesake, distinguished military service as an aviator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForNamesake Context triple: [William C. Maxwell, reasonForNamesake, distinguished military service as an aviator]
-
A.
reasonForName
chosen
Indicates the explanation or cause behind why an entity has a particular name.
-
B.
reasonForEpithet
Indicates the cause, motivation, or circumstance that explains why a particular epithet is applied to an entity.
-
C.
isNamedFor
Indicates that one entity bears its name in honor of, or derived from, another entity.
-
D.
causeOfCommemoration
Indicates that one entity is the reason or occasion for which another entity is commemorated or memorialized.
-
E.
hasToponymicMotivation
Indicates that something is motivated, derived, or named based on a place name (toponym).
- F. None of above.
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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de85afabe48190926d6098047f4bcf |
completed | April 14, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:12 a.m.