Triple
T31450672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qené poetry |
E802311
|
entity |
| Predicate | requiresSkillIn |
P6204
|
FINISHED |
| Object | biblical exegesis |
—
|
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: biblical exegesis | Statement: [Qené poetry, requiresSkillIn, biblical exegesis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresSkillIn Context triple: [Qené poetry, requiresSkillIn, biblical exegesis]
-
A.
requiresSkill
chosen
Indicates that performing or engaging in one entity (e.g., a task or role) depends on possessing or applying a specific skill represented by the other entity.
-
B.
requiresSkillLevel
Indicates that performing or engaging in something depends on possessing at least a specified level of skill.
-
C.
requiresExperienceIn
Indicates that one entity demands prior experience or expertise in another entity as a prerequisite or qualification.
-
D.
indicatesSkill
Indicates a relationship where one entity possesses, demonstrates, or is associated with a particular skill represented by another entity.
-
E.
skilledIn
Indicates that an entity possesses ability, expertise, or proficiency in performing or using another entity (such as a task, tool, or domain).
- 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_69f348c678ac81908a2e950867619061 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
Created at: April 30, 2026, 9:12 p.m.