Triple
T10497069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hegesias of Cyrene |
E247564
|
entity |
| Predicate | allegedBan |
P16813
|
FINISHED |
| Object | forbidden to lecture in Alexandria |
—
|
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: forbidden to lecture in Alexandria | Statement: [Hegesias of Cyrene, allegedBan, forbidden to lecture in Alexandria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedBan Context triple: [Hegesias of Cyrene, allegedBan, forbidden to lecture in Alexandria]
-
A.
bannedBy
Indicates that an entity is prohibited or disallowed as a result of a decision or action taken by another entity.
-
B.
bannedAfter
Indicates that one entity becomes prohibited or forbidden only after the occurrence or establishment of another specified entity or event.
-
C.
hasJetBan
Indicates that an entity is subject to a prohibition or restriction on the use or operation of jet aircraft.
-
D.
bannedInContextOf
Indicates that something is prohibited or not allowed specifically within a particular situation, setting, or scope.
-
E.
allegedStatus
chosen
Indicates that a particular status or condition is claimed or asserted about an entity, but has not been confirmed as true.
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5098cd82c8190b44127a66c9c75ae |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8e24ac8190912c9f11b8bd3084 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:24 p.m.