Triple
T34711252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meretnebty |
E1000650
|
entity |
| Predicate | possibleSocialRole |
P28457
|
FINISHED |
| Object | elite woman |
—
|
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: elite woman | Statement: [Meretnebty, possibleSocialRole, elite woman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleSocialRole Context triple: [Meretnebty, possibleSocialRole, elite woman]
-
A.
possibleRole
Indicates that an entity is capable of or eligible to serve in a particular role or function in a given context.
-
B.
socialRoleIn
Indicates that one entity holds a particular social role, status, or position within the context or framework defined by another entity.
-
C.
typicalRole
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
-
D.
possibleSocialStatus
chosen
Indicates that one entity may hold, attain, or be associated with a particular social status in relation to another context or system.
-
E.
otherRole
Indicates that an entity holds an additional or alternative role in relation to another entity, distinct from its primary role.
- 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_69f76dad3f108190a280fd0a2f4ee89a |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 3:59 p.m.