Triple
T5061951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles James Fox |
E114041
|
entity |
| Predicate | parliamentaryDebut |
P61034
|
FINISHED |
| Object | 1768 |
—
|
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: 1768 | Statement: [Charles James Fox, parliamentaryDebut, 1768]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parliamentaryDebut Context triple: [Charles James Fox, parliamentaryDebut, 1768]
-
A.
representedInParliamentSince
Indicates that an entity has held representation in a parliament continuously from a specified starting time.
-
B.
parliamentaryStatus
Indicates the relationship of whether and how an entity is formally recognized or holds standing within a parliamentary system or body.
-
C.
rankInParliament
Indicates the hierarchical position or level of authority that an individual holds within a parliamentary body.
-
D.
servedInParliamentFor
Indicates that a person held a parliamentary seat as a representative of a specified constituency, region, or jurisdiction.
-
E.
parliamentaryInvolvement
Indicates involvement or participation of an entity in the activities, processes, or functions of a parliament or parliamentary body.
- 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_69bd443c0c8c81908663b77afb28e165 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74740ae08190930f1fd57187334e |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd715622b48190a3e8e49a5ef62b4a |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd738ac2e0819099c06cdcc5e21d28 |
completed | March 20, 2026, 4:19 p.m. |
Created at: March 20, 2026, 1:38 p.m.