Triple
T34353535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merneferre Ay |
E881649
|
entity |
| Predicate | knownFromRegion |
P9687
|
FINISHED |
| Object | Upper Egypt |
—
|
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: Upper Egypt | Statement: [Merneferre Ay, knownFromRegion, Upper Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownFromRegion Context triple: [Merneferre Ay, knownFromRegion, Upper Egypt]
-
A.
knownFrom
Indicates that one entity is aware of, has learned about, or recognizes another entity through a specified source, context, or medium.
-
B.
knownIn
Indicates that an entity is recognized, acknowledged, or familiar within a particular context, domain, or group.
-
C.
foundInRegion
chosen
Indicates that something is located within, occurs in, or is associated with a specific geographic or spatial region.
-
D.
regionallyRecognizedBy
Indicates that an entity is officially or commonly acknowledged within a specific geographic region by a particular authority, organization, or community.
-
E.
mentionsRegion
Indicates that one entity explicitly refers to or cites a specific geographic region in its content or 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_69f349bd06008190904c2f86c42749e3 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: May 1, 2026, 1:58 a.m.