Triple
T4195658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karl Bühler |
E89146
|
entity |
| Predicate | languageFunction |
P38257
|
FINISHED |
| Object | representational 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: representational function | Statement: [Karl Bühler, languageFunction, representational function]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageFunction Context triple: [Karl Bühler, languageFunction, representational function]
-
A.
languageFeature
Indicates that one entity is a characteristic, property, or capability of a language associated with the other entity.
-
B.
usesFunction
chosen
Indicates that one entity employs, invokes, or relies on a particular function to perform an operation or achieve a result.
-
C.
languageName
Indicates the specific name assigned to a language in the relationship.
-
D.
languageProvision
Indicates that one entity supplies, supports, or makes available a particular language (or set of languages) for use by another entity.
-
E.
publicFunction
Indicates that a function or method is accessible from outside its defining scope, module, or class (i.e., it has public visibility).
- 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_69aed9569a4481908b6c1fcec2a11e21 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af035e87148190a0f0bf48b813ffaa |
completed | March 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69af01959c4881909eb1adcb3bdadbe6 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:46 p.m.