Triple
T17486951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peircean semiotics |
E425800
|
entity |
| Predicate | definesSemiosisAs |
P74447
|
FINISHED |
| Object | action of a sign |
—
|
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: action of a sign | Statement: [Peircean semiotics, definesSemiosisAs, action of a sign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesSemiosisAs Context triple: [Peircean semiotics, definesSemiosisAs, action of a sign]
-
A.
hasSemanticsDefinedBy
chosen
Indicates that the meaning or interpretation of one entity is specified, constrained, or determined by another entity.
-
B.
conceptualMeaning
Indicates the abstract idea, concept, or underlying significance that something represents or conveys.
-
C.
CISMeaning
Indicates that one concept, term, or symbol conveys, expresses, or stands for a particular meaning or interpretation in a given context.
-
D.
semanticsDetail
Indicates a more specific or fine-grained semantic characterization or nuance of a broader meaning or interpretation.
-
E.
semanticRootMeaning
Indicates the fundamental or core meaning that underlies a word, phrase, or expression in a semantic structure.
- 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451d2a5208190b25944626e779fdc |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.