Triple
T32214319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herbrand semantics |
E822886
|
entity |
| Predicate | varies |
P173847
|
FINISHED |
| Object | interpretations of predicate symbols |
—
|
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: interpretations of predicate symbols | Statement: [Herbrand semantics, varies, interpretations of predicate symbols]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: varies Context triple: [Herbrand semantics, varies, interpretations of predicate symbols]
-
A.
variesOver
Indicates that the value, state, or behavior of one entity changes as a function of another entity or parameter.
-
B.
viewVariesAmong
Indicates that the way something is viewed, perceived, or interpreted differs across multiple entities or contexts.
-
C.
variant
Indicates that one entity is an alternative form, version, or variation of another entity.
-
D.
varietyOf
Indicates that one entity is a specific type, kind, or variant of another, more general entity.
-
E.
usageVariesBy
Indicates that the way something is used differs depending on a specified factor, such as context, user, location, or conditions.
- F. None of above. chosen
Provenance (4 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bb95ffc48190bb4a7319a05834d6 |
completed | May 3, 2026, 3:05 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:37 a.m.