Triple
T7323731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Parliament |
E168814
|
entity |
| Predicate | canPetitionedBy |
P67728
|
FINISHED |
| Object | EU citizens |
—
|
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: EU citizens | Statement: [European Parliament, canPetitionedBy, EU citizens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canPetitionedBy Context triple: [European Parliament, canPetitionedBy, EU citizens]
-
A.
canBePetitionedBy
chosen
Indicates that an entity is eligible to receive formal petitions, requests, or appeals from another entity.
-
B.
containsPetition
Indicates that one entity includes or holds a petition within it, either as content or as a component.
-
C.
canElect
Indicates that one entity has the authority or ability to choose another entity for a position, role, or office through an election process.
-
D.
canBeAppealedTo
Indicates that a decision, action, or authority is subject to being challenged or reviewed by a higher or alternative authority through an appeal process.
-
E.
canApplyFor
Indicates that one entity has the eligibility or permission to submit a request or application for another entity or opportunity.
- 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_69c68a54cacc81908e3b773441f19566 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f046b93c8190a80dd48ee409ec5d |
completed | March 27, 2026, 9:01 p.m. |
| PD | Predicate disambiguation | batch_69c6e77230048190b2c29ca6b3a65b8e |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:03 p.m.