Triple
T28490265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific Star |
E720944
|
entity |
| Predicate | claspInscription |
P4758
|
FINISHED |
| Object | "BURMA" in raised letters on a bar |
—
|
NE NERFINISHED |
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: "BURMA" in raised letters on a bar | Statement: [Pacific Star, claspInscription, "BURMA" in raised letters on a bar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claspInscription Context triple: [Pacific Star, claspInscription, "BURMA" in raised letters on a bar]
-
A.
mayBeInscribedAs
Indicates that one entity is permitted or suitable to be formally recorded, written, or engraved as another entity.
-
B.
isInscribedOn
chosen
Indicates that text, symbols, or markings are written, carved, or otherwise permanently placed onto the surface of an object.
-
C.
inscribedFor
Indicates that something is formally written, engraved, or dedicated for a particular recipient or purpose.
-
D.
inscribedTogetherWith
Indicates that one entity is inscribed jointly with another on the same surface, object, or document as part of a single inscription context.
-
E.
methodOfInscription
Indicates the technique or process used to inscribe or engrave content onto a surface.
- 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64f1474588190a5d4f5cad8e3dba6 |
completed | May 2, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:01 a.m.