Triple
T37366911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Libyan Sibyl (sculpture) |
E927735
|
entity |
| Predicate | subjectFrom |
P195569
|
FINISHED |
| Object | classical mythology |
—
|
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 mythology | Statement: [The Libyan Sibyl (sculpture), subjectFrom, classical mythology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectFrom Context triple: [The Libyan Sibyl (sculpture), subjectFrom, classical mythology]
-
A.
subjectForm
Indicates that one entity is the physical or digital form, format, or manifestation in which the subject entity is presented or expressed.
-
B.
subjectOfMessages
Indicates that an entity is the main topic or focus about which the messages are written or communicated.
-
C.
subjectComposer
Indicates that the subject is the composer or creator of a musical work or composition.
-
D.
subjectCanBe
Indicates that the subject has the potential or capability to assume, become, or be classified as the specified object or state.
-
E.
subjectImpliedAs
Indicates that the subject of an action or statement is not explicitly stated but is understood or inferred from context.
- 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_69f76eb820248190a5c395ca50ad002a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69fdd922d73c81908ad3faade247ec16 |
completed | May 8, 2026, 12:37 p.m. |
Created at: May 3, 2026, 4:16 p.m.