Triple
T31909773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James S. Green |
E814646
|
entity |
| Predicate | servedInBody |
P198734
|
FINISHED |
| Object | United States Senate |
—
|
NE NERFINISHED |
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: United States Senate | Statement: [James S. Green, servedInBody, United States Senate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedInBody Context triple: [James S. Green, servedInBody, United States Senate]
-
A.
servesBody
Indicates that one entity provides service, assistance, or benefit directly to another entity.
-
B.
withinBody
Indicates that one entity is physically contained inside or located within the body of another entity.
-
C.
usesBody
Indicates that one entity employs or utilizes the physical body of another (or its own) as a means or instrument to perform an action or function.
-
D.
representsInBody
Indicates that something is depicted, expressed, or manifested within the physical body of an entity.
-
E.
bodyServesAsSettingFor
Indicates that a person’s or creature’s body functions as the physical environment or location in which an event, scene, or activity takes place.
- F. None of above. chosen
Provenance (4 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff0214d7348190904688376df99bce |
completed | May 9, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69feffd62fec8190a855922c8b3c57cf |
completed | May 9, 2026, 9:35 a.m. |
| PDg | Predicate description generation | batch_69ff02141dbc8190b00bcea2aa734b3a |
completed | May 9, 2026, 9:44 a.m. |
Created at: May 1, 2026, 12:01 a.m.