Triple
T38592167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scarab Lord |
E932478
|
entity |
| Predicate | realmSpecific |
P191642
|
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: [Scarab Lord, realmSpecific, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realmSpecific Context triple: [Scarab Lord, realmSpecific, true]
-
A.
realmType
Indicates the classification or category of a realm, specifying what kind or type of realm it is.
-
B.
realmWithin
Indicates that one realm or domain is contained inside, or exists as a subset of, another realm or domain.
-
C.
realmName
Indicates the designated name or title assigned to a particular realm or domain.
-
D.
realmCountContext
Indicates the contextual setting or scope in which a particular count of realms (or distinct domains) is defined or evaluated.
-
E.
regionSpecialization
Indicates that a region is designated or recognized as being particularly focused on, adapted to, or specialized in a specific function, activity, or domain.
- F. None of above. chosen
Provenance (4 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
| PDg | Predicate description generation | batch_69fce28a74508190aab36551094e8226 |
completed | May 7, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:32 p.m.