Triple
T15789890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyperbolicsyllabicsesquedalymistic |
E382835
|
entity |
| Predicate | hasTitleProperty |
P103300
|
FINISHED |
| Object | invented pseudo-scientific word |
—
|
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: invented pseudo-scientific word | Statement: [Hyperbolicsyllabicsesquedalymistic, hasTitleProperty, invented pseudo-scientific word]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleProperty Context triple: [Hyperbolicsyllabicsesquedalymistic, hasTitleProperty, invented pseudo-scientific word]
-
A.
hasTitleType
Indicates that an entity holds a specific kind or category of title (such as job title, honorific, or formal designation).
-
B.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
C.
hasTitleFeature
chosen
Indicates that an entity possesses a specific characteristic, attribute, or element related to its title.
-
D.
hasTitleFrom
Indicates that one entity holds or uses a title that originates from, or is conferred by, another entity.
-
E.
hasTitleRole
Indicates that an entity holds or is assigned a specific title or role in relation to 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e054048ff48190ad107c890ef73166 |
completed | April 16, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:48 a.m.