Triple
T6057313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baufra |
E134944
|
entity |
| Predicate | roleInSources |
P11527
|
FINISHED |
| Object | participant in tales before Khufu |
—
|
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: participant in tales before Khufu | Statement: [Baufra, roleInSources, participant in tales before Khufu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInSources Context triple: [Baufra, roleInSources, participant in tales before Khufu]
-
A.
roleInText
chosen
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
-
B.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
C.
role
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
-
D.
citationNetworkRole
Indicates the specific function or position an entity holds within a network of citations, such as how it contributes to or is characterized in the structure of citation relationships.
-
E.
collaboratorRole
Indicates the specific function, position, or capacity in which one collaborator participates in a shared activity or project with another.
- 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_69c00877b6d4819096b0e163728b73a3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0570d00e88190b2d8d596e40378d9 |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049edc6f0819092ca620d9073ad26 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:09 p.m.