Triple
T34533057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reichenbach epsilon |
E886591
|
entity |
| Predicate | isConventional |
P47902
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Reichenbach epsilon, isConventional, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConventional Context triple: [Reichenbach epsilon, isConventional, true]
-
A.
isArbitraryConvention
chosen
Indicates that the relationship or rule exists due to social or contextual agreement rather than inherent necessity or natural law.
-
B.
isTraditional
Indicates that something adheres to long-established customs, practices, or norms rather than modern or innovative ones.
-
C.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
-
D.
isCustomarily
Indicates that something typically or traditionally occurs, is done, or is used in a particular way according to custom or usual practice.
-
E.
conventionFor
Indicates a relationship where something serves as a standard, rule, or customary practice governing how another thing is done, represented, or interpreted.
- 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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 1, 2026, 2:02 a.m.