Triple
T2667890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ars Gratia Artis |
E55680
|
entity |
| Predicate | scriptPlacement |
P41557
|
FINISHED |
| Object | circular band around lion head |
—
|
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: circular band around lion head | Statement: [Ars Gratia Artis, scriptPlacement, circular band around lion head]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptPlacement Context triple: [Ars Gratia Artis, scriptPlacement, circular band around lion head]
-
A.
scriptRegion
Indicates a specific portion or segment within a script that is grouped or identified as a distinct region.
-
B.
scriptType
Indicates the classification or category of a script, specifying what kind of script it is (e.g., its format, purpose, or scripting language type).
-
C.
scriptStyle
Indicates that one entity specifies or characterizes the stylistic form or manner of a script associated with another entity.
-
D.
scriptCode
Indicates that an entity is associated with a particular writing system or script, identified by a standardized script code.
-
E.
scriptOnFlag
Indicates that a script is attached to and/or executed when a specific flag or condition is set.
- 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_69ab49e54de48190be708cd1cf8be073 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd98a4ee88190aa7ef914e316ba31 |
completed | March 7, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69abd8190ad481908f3e14ac84d0940a |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd8f98c348190a68064c565589459 |
completed | March 7, 2026, 7:51 a.m. |
Created at: March 6, 2026, 9:54 p.m.