Triple
T6507952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | İmroz |
E150057
|
entity |
| Predicate | wasMentionedIn |
P831
|
FINISHED |
| Object | classical antiquity sources |
—
|
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: classical antiquity sources | Statement: [İmroz, wasMentionedIn, classical antiquity sources]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasMentionedIn Context triple: [İmroz, wasMentionedIn, classical antiquity sources]
-
A.
mentionedWith
Indicates that two entities are mentioned together or in close association within the same context, such as a document, sentence, or conversation.
-
B.
eraMentioned
Indicates that a specific historical or temporal era is explicitly referenced or mentioned in a given context.
-
C.
mentionedAs
Indicates that one entity is referred to or cited by name or description in the context of another entity.
-
D.
mentions
chosen
Indicates that one entity refers to, cites, or brings up another entity in some form of communication or content.
-
E.
hasBeenSubjectOf
Indicates that an entity has previously been the focus or target of a particular action, process, or investigation.
- 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_69c687ef291081909d437f035eef1cda |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c69f386aa08190bfc8592a92ec6339 |
completed | March 27, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69c68ab714908190aa7c2fbf64078e15 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:43 p.m.