Triple
T17313939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Organon model of language |
E420371
|
entity |
| Predicate | appealFunctionAlsoCalled |
P40691
|
FINISHED |
| Object | signal function |
—
|
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: signal function | Statement: [Organon model of language, appealFunctionAlsoCalled, signal function]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appealFunctionAlsoCalled Context triple: [Organon model of language, appealFunctionAlsoCalled, signal function]
-
A.
alsoAppealsTo
Indicates that something attracts, interests, or is pleasing to an additional person, group, or audience beyond the primary one.
-
B.
appealsFor
Indicates that one entity formally requests support, intervention, or a favorable decision from another entity.
-
C.
appealBeyond
Indicates that something has significance, relevance, or attractiveness that extends beyond a specified scope, group, or context.
-
D.
calledAs
chosen
Indicates that one entity is referred to, named, or addressed by another specific name or label.
-
E.
appealsFrom
Indicates that a decision, judgment, or ruling is being challenged and taken to a higher authority or court for review.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4399b4dcc8190996d79d04ba88795 |
completed | April 19, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:43 a.m.