Triple
T34415711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinn |
E883397
|
entity |
| Predicate | inSentenceHasObject |
P73670
|
FINISHED |
| Object | truth-value as Bedeutung |
—
|
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: truth-value as Bedeutung | Statement: [Sinn, inSentenceHasObject, truth-value as Bedeutung]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inSentenceHasObject Context triple: [Sinn, inSentenceHasObject, truth-value as Bedeutung]
-
A.
objectOfVerb
chosen
Indicates that one entity serves as the direct object or recipient of the action expressed by a given verb in a clause.
-
B.
hasSubjectPosition
Indicates that an entity occupies or is assigned to a particular subject role or position within a structure, context, or organization.
-
C.
objet
Indicates that one entity is the object (recipient or target) of an action or relation performed by another entity.
-
D.
usesObjective
Indicates that an agent employs or applies a particular object, tool, or resource to carry out an action or achieve a goal.
-
E.
hasNoun
Indicates that an entity possesses or is associated with a specific noun as an attribute, label, or grammatical component.
- 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_69f349c2e3b88190a67834eb5bcffeaf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71947ad88819082ab9d85dd493b01 |
completed | May 3, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:59 a.m.