Triple
T15672291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nemean Lion |
E377343
|
entity |
| Predicate | sometimesSaidToBe |
P38176
|
FINISHED |
| Object | offspring of Orthrus |
—
|
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: offspring of Orthrus | Statement: [Nemean Lion, sometimesSaidToBe, offspring of Orthrus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sometimesSaidToBe Context triple: [Nemean Lion, sometimesSaidToBe, offspring of Orthrus]
-
A.
sometimesSpeaks
Indicates that one entity speaks to or communicates with another only on some occasions, rather than regularly or consistently.
-
B.
saidBy
Indicates that a particular statement, quote, or utterance was spoken or produced by a specific entity.
-
C.
oftenSays
Indicates that one entity frequently makes a particular statement or remark, or regularly expresses a certain idea or phrase.
-
D.
oftenHeldToBe
chosen
Indicates that something is frequently regarded, considered, or believed to be a certain way by many people or in many contexts.
-
E.
oftenStatedWith
Indicates that one statement, fact, or expression is frequently mentioned or asserted together with another.
- 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f13b1b08190beabc9f4098aa096 |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:16 a.m.