Triple
T9103275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindon |
E218410
|
entity |
| Predicate | returned |
P16989
|
FINISHED |
| Object | two Members of Parliament |
—
|
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: two Members of Parliament | Statement: [Hindon, returned, two Members of Parliament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returned Context triple: [Hindon, returned, two Members of Parliament]
-
A.
returnedBy
Indicates that something is given, sent, or brought back to a previous sender, owner, or source by another entity.
-
B.
returnedDuring
Indicates that one entity was given back or restored to another entity within a specified time period or event.
-
C.
returnedFrom
chosen
Indicates that an entity has come back or been sent back from a specified source, location, or prior state.
-
D.
returnedVia
Indicates that something was sent back or responded to through a specified medium, channel, or method.
-
E.
wasReturnedTo
Indicates that an entity was sent or brought back to a previous owner, location, or state after having been away or removed.
- 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_69ca83db7448819090d0a5de842ef2ac |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc9715d5188190bce68d095e10c2eb |
completed | April 1, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:15 p.m.