Triple
T36388434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFQ Level 5 |
E896261
|
entity |
| Predicate | typicalProviders |
P17473
|
FINISHED |
| Object | secondary schools |
—
|
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: secondary schools | Statement: [NFQ Level 5, typicalProviders, secondary schools]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalProviders Context triple: [NFQ Level 5, typicalProviders, secondary schools]
-
A.
typicalProvider
chosen
Indicates that one entity commonly or characteristically serves as a provider of goods, services, or resources to another entity.
-
B.
providerOf
Indicates that one entity supplies, furnishes, or makes available a good, service, or resource to another entity.
-
C.
typicalEmployer
Indicates that one entity is the kind of organization or person that commonly or usually employs the other entity.
-
D.
typicalDomain
Indicates that one entity is the characteristic or most common domain, context, or area of application in which another entity typically occurs or is used.
-
E.
typicalAffiliates
Indicates that one entity is commonly or characteristically associated, aligned, or partnered 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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.