Triple
T3098584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book of Signs |
E64659
|
entity |
| Predicate | hasInterpretiveFramework |
P33381
|
FINISHED |
| Object | signs as symbolic actions |
—
|
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: signs as symbolic actions | Statement: [Book of Signs, hasInterpretiveFramework, signs as symbolic actions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInterpretiveFramework Context triple: [Book of Signs, hasInterpretiveFramework, signs as symbolic actions]
-
A.
containsInterpretationOf
chosen
Indicates that one entity includes or embodies an interpretation or understanding of another entity.
-
B.
isInterpretedBy
Indicates that something (such as data, a work, or a signal) is given meaning, understanding, or explanation by a particular agent or process.
-
C.
hasInterpretiveSigns
Indicates that interpretive or informational signs are present at or associated with the subject.
-
D.
interpretationMethod
Indicates the method, technique, or process used to interpret or derive meaning from something.
-
E.
hasDistinctiveFrameworkWith
Indicates that one entity possesses a unique or distinguishing structural framework in relation to another entity.
- 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_69ad857dc98481909e585dc3372e3ed5 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada23dde988190a1aca020685594f3 |
completed | March 8, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69ad9df06ed88190809f0683122caa5a |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:03 p.m.