Triple
T19026469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ABVP |
E465621
|
entity |
| Predicate | positionOnIssues |
P20467
|
FINISHED |
| Object | support for uniform civil code |
—
|
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: support for uniform civil code | Statement: [ABVP, positionOnIssues, support for uniform civil code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnIssues Context triple: [ABVP, positionOnIssues, support for uniform civil code]
-
A.
positionOnIssue
chosen
Indicates the stance or viewpoint an entity holds regarding a specific issue or topic.
-
B.
positionOnReason
Indicates that one entity holds a particular stance, justification, or rationale concerning another entity or issue.
-
C.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
D.
positionOnRights
Indicates a stance, opinion, or policy an entity holds regarding rights (such as legal, human, or civil rights).
-
E.
addressesIssue
Indicates that one entity deals with, responds to, or attempts to resolve a specific issue associated with 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d73cace0819096bdac6dc8c17253 |
completed | April 20, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.