Triple
T19210433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andromaque |
E480342
|
entity |
| Predicate | sourceDInspiration |
P41791
|
FINISHED |
| Object | mythologie grecque |
—
|
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: mythologie grecque | Statement: [Andromaque, sourceDInspiration, mythologie grecque]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceDInspiration Context triple: [Andromaque, sourceDInspiration, mythologie grecque]
-
A.
hasInspirationSource
chosen
Indicates that something derives its creative motivation, ideas, or influence from a particular source.
-
B.
settingInspiration
Indicates that one entity serves as the creative or motivational source for the setting or environment of another entity.
-
C.
genreOfInspiration
Indicates that one entity serves as the inspirational genre or stylistic source for the creation, style, or classification of another entity.
-
D.
creativeSearch
Indicates that an entity performs or engages in a search process that involves creativity, exploration, or the generation of novel ideas or solutions.
-
E.
intelligenceSource
Indicates that one entity serves as the origin or provider of intelligence information for another entity.
- 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5f9a0d1248190953e36e44f0cafdd |
completed | April 20, 2026, 10:02 a.m. |
| PD | Predicate disambiguation | batch_69e4dcf22b3c8190bee02e3af946e114 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:21 p.m.