Triple
T28527138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linb |
E721936
|
entity |
| Predicate | hasScriptScope |
P178034
|
FINISHED |
| Object | entire Linear B script |
—
|
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: entire Linear B script | Statement: [Linb, hasScriptScope, entire Linear B script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScriptScope Context triple: [Linb, hasScriptScope, entire Linear B script]
-
A.
hasScriptCode
Indicates that an entity is associated with a particular writing system identified by a specific script code.
-
B.
containsScript
Indicates that one entity includes or embeds the script of another entity within it.
-
C.
hasScriptBy
Indicates that one entity has its script authored, written, or created by another entity.
-
D.
hasScriptPropertyValue
Indicates that a script-related property of an entity is assigned a specific value.
-
E.
hasScriptUsage
Indicates that one entity uses, employs, or is written in the script or writing system specified by another entity.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f707f380388190954b79d52a321921 |
completed | May 3, 2026, 8:31 a.m. |
Created at: April 28, 2026, 3:25 a.m.