Triple
T14810697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GECF Statute |
E348169
|
entity |
| Predicate | isLegalBasisFor |
P125
|
FINISHED |
| Object | GECF governance system |
—
|
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: GECF governance system | Statement: [GECF Statute, isLegalBasisFor, GECF governance system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLegalBasisFor Context triple: [GECF Statute, isLegalBasisFor, GECF governance system]
-
A.
legalBasis
chosen
Indicates the legal rule, authority, or justification under which an action, decision, or status is established or carried out.
-
B.
hasLegalBasisSince
Indicates that something has had a valid legal foundation or authority starting from a specified point in time.
-
C.
legalBasisForExecution
Indicates that one entity serves as the legal justification or authority for carrying out the execution of another entity or action.
-
D.
predecessorLegalBasis
Indicates that one legal basis directly precedes and forms the prior legal foundation for another legal basis.
-
E.
hasLegalAuthorityFrom
Indicates that one entity possesses formal legal power, rights, or authorization that originates from or is granted 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decf35a5e081909321193ef37099d1 |
completed | April 14, 2026, 11:35 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:46 a.m.