Triple
T23722009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ptahhotep |
E586168
|
entity |
| Predicate | conceptsEmphasized |
P24015
|
FINISHED |
| Object | Maat |
—
|
NE NERFINISHED |
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: Maat | Statement: [Ptahhotep, conceptsEmphasized, Maat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conceptsEmphasized Context triple: [Ptahhotep, conceptsEmphasized, Maat]
-
A.
thematicConcept
Indicates that one entity embodies, expresses, or is centrally concerned with a particular underlying theme or conceptual idea represented by the other entity.
-
B.
introducedConcept
Indicates that one entity is responsible for presenting, defining, or bringing a new concept into use or awareness for another entity or context.
-
C.
primaryConcept
Indicates that one concept is the main or central idea in relation to another concept or context.
-
D.
skillEmphasis
Indicates that a particular skill is given special focus, priority, or importance within a context such as a role, task, or curriculum.
-
E.
featuredConcept
chosen
Indicates that one concept is highlighted or given special prominence relative to others in a particular context.
- 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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b91177c08190bea6e62ed13e2495 |
completed | April 29, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:04 p.m.