Triple
T7299233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celtic studies |
E167798
|
entity |
| Predicate | studiesPeople |
P76079
|
FINISHED |
| Object | Celtic-speaking peoples |
—
|
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: Celtic-speaking peoples | Statement: [Celtic studies, studiesPeople, Celtic-speaking peoples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studiesPeople Context triple: [Celtic studies, studiesPeople, Celtic-speaking peoples]
-
A.
studiedBy
Indicates that a subject (such as a field, topic, or object) is examined, researched, or learned by an agent (such as a person or group).
-
B.
researchUser
Indicates that an entity conducts research on, studies, or investigates a particular user.
-
C.
widelyStudiedIn
Indicates that something has been extensively researched, analyzed, or examined within a particular field, domain, or context.
-
D.
studiesConcept
Indicates that an entity engages in learning, examining, or researching a particular concept.
-
E.
studiedWithin
Indicates that one entity pursued studies or academic work within the scope, context, or boundaries defined by another entity (such as an institution, program, or field).
- F. None of above. chosen
Provenance (4 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_69c6888c820881909fc68f689fe1c251 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebad1b4481909e49ccc580007e4b |
completed | March 27, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6eb2d4c0c8190b4cc6fdfdb7f4827 |
completed | March 27, 2026, 8:40 p.m. |
Created at: March 27, 2026, 3 p.m.