Triple
T5260193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth-shaker |
E118803
|
entity |
| Predicate | typeOfEpithet |
P5567
|
FINISHED |
| Object | descriptive epithet |
—
|
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: descriptive epithet | Statement: [Earth-shaker, typeOfEpithet, descriptive epithet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfEpithet Context triple: [Earth-shaker, typeOfEpithet, descriptive epithet]
-
A.
languageOfEpithet
Indicates the language in which an epithet (such as a descriptive or honorary title) is expressed.
-
B.
epithetOrTitle
Indicates that one entity serves as an epithet, honorific, or formal title used to designate or characterize another entity.
-
C.
reasonForEpithet
Indicates the cause, motivation, or circumstance that explains why a particular epithet is applied to an entity.
-
D.
honorificType
Indicates the type or category of honorific or formal title associated with an entity in a given context.
-
E.
termType
chosen
Indicates the classification or category of a term within a system, specifying what kind of term it is (e.g., type, role, or function) in relation to others.
- 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.