Triple
T15741574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latin I |
E381613
|
entity |
| Predicate | oftenOfferedBy |
P65734
|
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: [Latin I, oftenOfferedBy, secondary schools]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenOfferedBy Context triple: [Latin I, oftenOfferedBy, secondary schools]
-
A.
offeredIn
Indicates that something is made available or provided within a particular context, setting, or medium.
-
B.
oftenProvides
chosen
Indicates that one entity frequently or regularly supplies, offers, or makes another entity available.
-
C.
associatedOffering
Indicates a relationship where one offering is linked or connected to another offering as related or contextually relevant.
-
D.
usedAsOfferingAt
Indicates that something is employed or presented as an offering in a particular context, place, or event.
-
E.
officeredBy
Indicates that a person or group serves as the officers or commanding staff responsible for leading, managing, or administering another entity (such as an organization, unit, or vessel).
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0052c6208819098165d61d378d13b |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:46 a.m.