Triple
T6287343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAO 94027 |
E140931
|
entity |
| Predicate | isEyeOfBullInMythology |
P45276
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [SAO 94027, isEyeOfBullInMythology, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEyeOfBullInMythology Context triple: [SAO 94027, isEyeOfBullInMythology, true]
-
A.
hasEyes
Indicates that an entity possesses eyes as physical features.
-
B.
hasSimilarMythicalCreature
Indicates that two entities are associated with mythical creatures that share comparable characteristics, roles, or symbolic meanings.
-
C.
usesMythOf
Indicates that one entity employs or invokes a myth or mythical narrative about another entity as part of its actions, explanations, or representations.
-
D.
hasMythologicalOpponents
Indicates that one entity is opposed or challenged by another entity within a mythological or legendary context.
-
E.
hasMythologicalFeature
chosen
Indicates that an entity possesses a characteristic, attribute, or element derived from mythology or mythological beings.
- 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_69c008cd17c8819082b82d3fbeb68047 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063ff9f74819088dc603f56fc930c |
completed | March 22, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69c0560a0270819098ad2785b91e8f39 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:26 p.m.