Triple
T29119647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Dorwin |
E737143
|
entity |
| Predicate | expertiseClaim |
P87264
|
FINISHED |
| Object | ancient history |
—
|
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: ancient history | Statement: [Lord Dorwin, expertiseClaim, ancient history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expertiseClaim Context triple: [Lord Dorwin, expertiseClaim, ancient history]
-
A.
basedOnExpertiseOf
Indicates that something is determined, derived, or justified using the knowledge, skills, or judgment of a particular expert or group of experts.
-
B.
skilledIn
chosen
Indicates that an entity possesses ability, expertise, or proficiency in performing or using another entity (such as a task, tool, or domain).
-
C.
examinesClaim
Indicates that one entity reviews, inspects, or evaluates a claim made by another entity.
-
D.
scopeClaim
Indicates that a claim or statement applies within a specified scope, context, or boundary.
-
E.
claimedIn
Indicates that a statement, fact, or assertion is reported or documented within a particular source, document, or claim.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 11:24 a.m.