Triple
T19025593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unionist Party (Punjab) |
E465601
|
entity |
| Predicate | crossCommunal |
P133607
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Unionist Party (Punjab), crossCommunal, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossCommunal Context triple: [Unionist Party (Punjab), crossCommunal, true]
-
A.
communalAspect
Indicates that something involves or emphasizes shared participation, ownership, or experience within a group or community.
-
B.
crossCut
Indicates that one entity intersects or passes through another, typically cutting across it from one side to the other.
-
C.
crossBorderCommunity
Indicates a relationship where a community spans or connects populations across one or more political or geographic borders.
-
D.
crossWith
Indicates that one entity intersects or passes over/through the path, boundary, or position of another entity.
-
E.
community
Indicates a relationship where individuals or groups are connected by shared location, interests, or identity, forming a collective social unit.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6e271848190b67ad08af35b6796 |
completed | April 20, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8f6f7c8190af645bf08823ee2b |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 12:02 p.m.