Triple
T8812500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Folk-lore Filipino |
E209699
|
entity |
| Predicate | scholarlyApproach |
P1717
|
FINISHED |
| Object | comparative folklore |
—
|
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: comparative folklore | Statement: [El Folk-lore Filipino, scholarlyApproach, comparative folklore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scholarlyApproach Context triple: [El Folk-lore Filipino, scholarlyApproach, comparative folklore]
-
A.
scholarlyView
Indicates that one entity holds an academic or research-based interpretation, opinion, or theoretical stance about another entity.
-
B.
scholarlyUse
Indicates that something is used for academic, educational, or research-related purposes.
-
C.
academicApproach
Indicates an entity’s characteristic method, strategy, or style used in academic work, study, or instruction.
-
D.
scholarlyWork
Indicates a relationship where an entity is a formal academic or research work produced, published, or recognized within a scholarly context.
-
E.
researchApproach
chosen
Indicates the methodological strategy or set of methods used to conduct and structure a research activity or investigation.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5feed07881909bbe116ae359346a |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1f28ec8190a34311cb412920c2 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:45 p.m.