Triple
T26694593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coptic Menfe |
E672981
|
entity |
| Predicate | usedInLateAntiquity |
P175303
|
FINISHED |
| Object | 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: Egypt | Statement: [Coptic Menfe, usedInLateAntiquity, Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInLateAntiquity Context triple: [Coptic Menfe, usedInLateAntiquity, Egypt]
-
A.
statusInLateAntiquity
Indicates the social, political, or cultural standing that an entity held during the historical period of Late Antiquity.
-
B.
usedInRomanPeriodFor
Indicates that something served a particular function, purpose, or application during the Roman period.
-
C.
discoveredInAntiquity
Indicates that something was found, identified, or recognized during ancient historical times rather than in the modern era.
-
D.
regionDuringAntiquity
Indicates that one entity functioned as a geographic or political region during the historical period of antiquity.
-
E.
reputationInAntiquity
Indicates the reputation or standing an entity had during ancient times.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6d1d916f881909575c2b22c416a5b |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d0d331dc8190be5aa6bfc6365e67 |
completed | May 3, 2026, 4:36 a.m. |
Created at: April 27, 2026, 3:28 a.m.