Triple
T9556605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of Turkey (1961) |
E230554
|
entity |
| Predicate | placedUnderGuarantee |
P52798
|
FINISHED |
| Object | university autonomy |
—
|
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: university autonomy | Statement: [Constitution of Turkey (1961), placedUnderGuarantee, university autonomy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placedUnderGuarantee Context triple: [Constitution of Turkey (1961), placedUnderGuarantee, university autonomy]
-
A.
haveWarranty
Indicates that one entity provides or is covered by a warranty in relation to another entity.
-
B.
warrantyType
Indicates the specific category or kind of warranty associated with a product, service, or agreement.
-
C.
warrantyClause
Indicates that a contractual provision defines the scope, conditions, and duration of a warranty obligation between parties.
-
D.
hasWarrantyDisclaimer
Indicates that a product, service, or agreement includes a statement limiting or denying warranties or liability.
-
E.
guaranteeStatus
chosen
Indicates the current state or condition of a guarantee associated with an entity or agreement.
- 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_69ca847d3be8819099c9dad2a7e786f1 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9946c7b8819082f3a4ec4fc979e6 |
completed | April 1, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69ccd594d0ac8190a81bc11a3a538167 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:03 p.m.