Triple
T25331987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singur |
E635173
|
entity |
| Predicate | landReturnedTo |
P113523
|
FINISHED |
| Object | original landowners |
—
|
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: original landowners | Statement: [Singur, landReturnedTo, original landowners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landReturnedTo Context triple: [Singur, landReturnedTo, original landowners]
-
A.
leasedLandFor
Indicates that one party has granted another party the right to use a piece of land for a specified period under a lease agreement.
-
B.
returnedTerritoryName
Indicates the name of a territory that has been given back or restored to a previous owner or controlling entity.
-
C.
landHandedBackToTraditionalOwners
chosen
Indicates that control or ownership of land has been formally returned to its original Indigenous or traditional custodians.
-
D.
wasReturnedTo
Indicates that an entity was sent or brought back to a previous owner, location, or state after having been away or removed.
-
E.
wasRecapturedBy
Indicates that an entity which had previously escaped or been released was caught again by another entity.
- 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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f497c72ffc81908aa380376bb068d3 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:30 p.m.