Triple
T27101727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harisena |
E686458
|
entity |
| Predicate | roleInInscription |
P165140
|
FINISHED |
| Object | composer |
—
|
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: composer | Statement: [Harisena, roleInInscription, composer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInInscription Context triple: [Harisena, roleInInscription, composer]
-
A.
roleInName
Indicates that a specific role, title, or position is included as part of an entity’s name or naming expression.
-
B.
signatureRole
Indicates the specific function or capacity in which an entity participates in a signing or signature-related action.
-
C.
roleAccordingTo
Indicates that an entity holds a particular role or function as defined or interpreted by a specified source or perspective.
-
D.
roleOn
chosen
Indicates that an entity holds or performs a specific role or function within another entity, context, or activity.
-
E.
dedicateeRole
Indicates the specific role or capacity in which a person is honored or addressed as the dedicatee of a work or object.
- 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_69ef1489f8b481908e24a1985982bd26 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: April 27, 2026, 8:48 a.m.