Triple
T26305409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Kab |
E661667
|
entity |
| Predicate | primaryCult |
P195264
|
FINISHED |
| Object | vulture goddess Nekhbet |
—
|
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: vulture goddess Nekhbet | Statement: [El Kab, primaryCult, vulture goddess Nekhbet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCult Context triple: [El Kab, primaryCult, vulture goddess Nekhbet]
-
A.
primaryCulture
Indicates the main or dominant culture associated with an entity, typically in contrast to any secondary or additional cultures.
-
B.
primaryServes
Indicates that one entity’s main or principal function is to serve, support, or provide service to another entity.
-
C.
primaryCatch
Indicates that an entity is the main or most significant target, recipient, or object captured or obtained in a given context.
-
D.
primaryArea
Indicates that one entity is the main or most important area, domain, or field associated with another entity.
-
E.
primaryHeir
Indicates that one entity is the main or principal inheritor of another entity’s estate, title, or rights.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
| PDg | Predicate description generation | batch_69fdb4544b548190b8971f8055d48caa |
completed | May 8, 2026, 10 a.m. |
Created at: April 26, 2026, 10:18 p.m.