Triple
T38592128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scarab Wall |
E932477
|
entity |
| Predicate | openingGrants |
P194647
|
FINISHED |
| Object | Scarab Lord title |
—
|
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: Scarab Lord title | Statement: [Scarab Wall, openingGrants, Scarab Lord title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingGrants Context triple: [Scarab Wall, openingGrants, Scarab Lord title]
-
A.
openingContribution
Indicates that an entity makes an initial or first contribution to an activity, project, or discussion.
-
B.
openingPublication
Indicates that an entity is the initial or first publication in which another entity (such as a work, concept, or result) was formally made public.
-
C.
opens
Indicates that one entity causes or allows another entity (such as an object, space, or resource) to become accessible or no longer closed.
-
D.
openingWorkOf
Indicates that one work serves as the first or introductory piece in relation to another work, such as the opening item in a sequence or collection.
-
E.
openingTo
Indicates that one entity serves as an entrance, access point, or passage leading into or toward another entity.
- 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_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
| PDg | Predicate description generation | batch_69fd7e35967081909f8bc8389d976ffd |
completed | May 8, 2026, 6:09 a.m. |
Created at: May 3, 2026, 4:32 p.m.