Triple
T5432001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palamon |
E121516
|
entity |
| Predicate | relativeObscurity |
P43114
|
FINISHED |
| Object | obscure figure in Greek mythology |
—
|
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: obscure figure in Greek mythology | Statement: [Palamon, relativeObscurity, obscure figure in Greek mythology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeObscurity Context triple: [Palamon, relativeObscurity, obscure figure in Greek mythology]
-
A.
relativeNotability
Indicates how notable or prominent one entity is in comparison to another entity or set of entities.
-
B.
relativeLevel
Indicates a comparative relationship specifying how one entity’s level, degree, or intensity of some property stands relative to that of another entity.
-
C.
popularity
Indicates how widely liked, admired, or favored something or someone is by a group of people.
-
D.
hasLimitedRecognition
chosen
Indicates that the subject is acknowledged or accepted only to a small extent, in restricted contexts, or by a limited audience.
-
E.
blindedBy
Indicates that one entity causes another to lose the ability to see or perceive clearly, either literally or metaphorically.
- 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_69bd463c65f0819082ee6483ab4b466a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8911a7348190ad9378a248190f07 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd846b8bdc81909dcdc2a3084226f2 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:06 p.m.