Triple
T24709137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shureimon |
E611979
|
entity |
| Predicate | hasInscriptionMeaning |
P11402
|
FINISHED |
| Object | observing propriety |
—
|
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: observing propriety | Statement: [Shureimon, hasInscriptionMeaning, observing propriety]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInscriptionMeaning Context triple: [Shureimon, hasInscriptionMeaning, observing propriety]
-
A.
hasInscriptions
Indicates that an object, surface, or artifact bears written, carved, or engraved inscriptions on it.
-
B.
inscriptionMeaning
chosen
Indicates that an inscription conveys a particular meaning, message, or content.
-
C.
mayBeInscribedAs
Indicates that one entity is permitted or suitable to be formally recorded, written, or engraved as another entity.
-
D.
hasTitleInInscription
Indicates that an entity is mentioned with a specific title or designation within an inscription.
-
E.
hasDesignationMeaning
Indicates that one designation, label, or title conveys or corresponds to a particular meaning or semantic interpretation.
- 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_69e2c4d9c24c8190a3712d74327f0c6e |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 3:24 a.m.