Triple
T7066807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyrian purple |
E164372
|
entity |
| Predicate | lightfastness |
P74819
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Tyrian purple, lightfastness, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lightfastness Context triple: [Tyrian purple, lightfastness, high]
-
A.
lightType
Indicates the specific category or kind of light associated with an entity or lighting setup.
-
B.
lightingCharacteristic
Indicates the specific qualities or properties of how something is lit, such as brightness, color, direction, or style of illumination.
-
C.
lightPath
Indicates the route or trajectory that light follows as it travels between entities or through a medium.
-
D.
luxMeans
Indicates that something serves as a means, method, or instrument by which a specified light-related effect, condition, or outcome is achieved.
-
E.
preferredLight
Indicates that one entity favors or is best suited to a particular lighting condition or level of illumination.
- 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_69c688796c148190adb2f1596f595f22 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4a737dc8190add7f0228cb28111 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bdc1f08190975fcdbbb1854d1e |
completed | March 27, 2026, 7:59 p.m. |
| PDg | Predicate description generation | batch_69c6e4a15b088190bee9a23e94aaac53 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:39 p.m.