Triple
T38326051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austrian universities |
E1036786
|
entity |
| Predicate | alsoOfferInstructionIn |
P162709
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Austrian universities, alsoOfferInstructionIn, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoOfferInstructionIn Context triple: [Austrian universities, alsoOfferInstructionIn, English]
-
A.
mayOfferInstructionIn
chosen
Indicates that an entity is permitted or authorized to provide instruction or teaching in a particular subject, field, or context.
-
B.
mayBeOfferedFor
Indicates that one entity can potentially be provided or made available as an option to another entity.
-
C.
offeredInstructionComparableTo
Indicates that one party provided instruction or training that is comparable in content, level, or quality to that provided by another party.
-
D.
offersInterface
Indicates that one entity provides or exposes a specific interface that another entity can use or interact with.
-
E.
offering
Indicates that one entity presents or provides something to another entity, typically as a gift, contribution, or proposal.
- 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_69f76e1c16fc8190bde982289dd5106b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.