Triple
T35021552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patiala and East Punjab States Union |
E1010208
|
entity |
| Predicate | hadPrincelyComponents |
P182485
|
FINISHED |
| Object | Phulkian States |
—
|
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: Phulkian States | Statement: [Patiala and East Punjab States Union, hadPrincelyComponents, Phulkian States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPrincelyComponents Context triple: [Patiala and East Punjab States Union, hadPrincelyComponents, Phulkian States]
-
A.
hadPrincipality
Indicates that an entity possessed or governed a principality as its domain or territory.
-
B.
hadPrincelyRulersIntegrated
Indicates that an entity was governed by princely rulers who were incorporated into a larger political or administrative structure.
-
C.
holderIsPrince
Indicates that the holder of something has the royal status or title of a prince.
-
D.
princelyAgency
Indicates a relationship in which an entity acts with the authority, representation, or delegated power of a prince or princely office.
-
E.
hasNumberOfPalaces
Indicates the specific count of palaces associated with an entity.
- 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_69f76dccf0108190af43b465d3750196 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78dbf72648190a4971a558e9d1889 |
completed | May 3, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78ce43094819093857fc99f269afe |
completed | May 3, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4:01 p.m.