Triple
T10337834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Egyptian |
E243052
|
entity |
| Predicate | alsoUsedAfterSpokenPhase |
P26625
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Middle Egyptian, alsoUsedAfterSpokenPhase, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoUsedAfterSpokenPhase Context triple: [Middle Egyptian, alsoUsedAfterSpokenPhase, yes]
-
A.
isSpokenAlong
Indicates that something (typically a language or dialect) is used or spoken in the regions or areas that follow a particular path, boundary, or route.
-
B.
possiblySpokenAt
Indicates that an utterance or speech event may have occurred at a particular time or location, but this association is uncertain or not definitively confirmed.
-
C.
usedDuring
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
D.
usedAfterNameOf
chosen
Indicates that something is used immediately following the mention or specification of a name.
-
E.
spokenUntil
Indicates that an act of speaking or verbal communication continues up to a specific time or event and then stops.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e91fdb2081909866c6ecf417d75a |
completed | April 7, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69d4df9dc3208190bf1bd106f44f6202 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 11:54 a.m.