Triple
T17486968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peircean semiotics |
E425800
|
entity |
| Predicate | classifiesSignByCategory |
P74189
|
FINISHED |
| Object | qualisign |
—
|
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: qualisign | Statement: [Peircean semiotics, classifiesSignByCategory, qualisign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classifiesSignByCategory Context triple: [Peircean semiotics, classifiesSignByCategory, qualisign]
-
A.
classificationAccordingTo
Indicates that an entity is assigned a particular class, type, or category as defined or determined by a specified source, standard, or authority.
-
B.
signType
chosen
Indicates the specific category or kind of sign involved in the relationship or action.
-
C.
areClassifiedBy
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
-
D.
classificationLetter
Indicates that an entity is assigned a specific letter-based category or grade as its classification.
-
E.
recognizedSignLanguage
Indicates that one entity has correctly identified or understood a sign language used or produced by 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_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.