Triple
T5260175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth-shaker |
E118803
|
entity |
| Predicate | highlightsAspectOf |
P3362
|
FINISHED |
| Object | Poseidon as god of earthquakes |
—
|
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: Poseidon as god of earthquakes | Statement: [Earth-shaker, highlightsAspectOf, Poseidon as god of earthquakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highlightsAspectOf Context triple: [Earth-shaker, highlightsAspectOf, Poseidon as god of earthquakes]
-
A.
honorsAspectOf
Indicates that one entity shows respect, recognition, or reverence specifically toward a particular aspect, quality, or facet of another entity.
-
B.
highlights
chosen
Indicates that one entity draws special attention to, emphasizes, or visually marks another entity as important or noteworthy.
-
C.
governsAspectOf
Indicates that one entity exercises control, regulation, or determining influence over a particular aspect or component of another entity.
-
D.
hasProminentAspect
Indicates that an entity possesses a particularly notable, dominant, or emphasized aspect or feature.
-
E.
notableFeatureOn
Indicates that one entity is a prominent or distinguishing feature located on or part of 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bcced6881909bdb7ac5471a37fe |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:50 p.m.