Triple
T8229580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linear B |
E192255
|
entity |
| Predicate | hasSignType |
P64196
|
FINISHED |
| Object | syllabic signs |
—
|
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: syllabic signs | Statement: [Linear B, hasSignType, syllabic signs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignType Context triple: [Linear B, hasSignType, syllabic signs]
-
A.
hasSignTypes
chosen
Indicates that an entity is associated with one or more specific types or categories of signs.
-
B.
hasSign
Indicates that an entity possesses, displays, or is associated with a particular sign or symbol.
-
C.
hasSignFor
Indicates that one entity displays, bears, or provides a sign, symbol, or notice that represents, directs attention to, or gives information about another entity.
-
D.
signType
Indicates the specific category or kind of sign involved in the relationship or action.
-
E.
signatoryType
Indicates the specific role or category of a party that has signed or formally agreed to a document, contract, or agreement.
- 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_69ca82db5b90819085d1ad7c2e27bfcc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7802417c81908837c31136c41a5c |
completed | March 31, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69cb36b1dea0819091418072501e79c1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:46 p.m.