Triple
T473179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilocano language |
E9002
|
entity |
| Predicate | hasLiterature |
P2989
|
FINISHED |
| Object | oral literature tradition |
—
|
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: oral literature tradition | Statement: [Ilocano language, hasLiterature, oral literature tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiterature Context triple: [Ilocano language, hasLiterature, oral literature tradition]
-
A.
hasLiteraryForm
Indicates that one entity is expressed, structured, or realized in a particular literary form (such as a genre, style, or textual format).
-
B.
literarySource
Indicates that one entity serves as the written or literary origin, reference, or basis for another entity.
-
C.
hasPublication
Indicates that an entity is associated with or responsible for a specific publication.
-
D.
literaryTradition
chosen
Indicates a relationship where a work, practice, or expression belongs to, arises from, or participates in a particular established body of literary customs, styles, or conventions.
-
E.
yearLit
Indicates the year in which something was illuminated, lit, or first had lighting installed or activated.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0208c788190a96cdabcf593fda7 |
completed | Feb. 28, 2026, 1:39 p.m. |
| PD | Predicate disambiguation | batch_69a2edecefb081908331ef8b9edf6636 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.