Triple
T285917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silver Rule |
E5883
|
entity |
| Predicate | isExpressedAs |
P4596
|
FINISHED |
| Object | negative reciprocity principle |
—
|
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: negative reciprocity principle | Statement: [Silver Rule, isExpressedAs, negative reciprocity principle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isExpressedAs Context triple: [Silver Rule, isExpressedAs, negative reciprocity principle]
-
A.
interpretedAs
Indicates that something is understood, perceived, or taken to mean something else, often based on context or subjective judgment.
-
B.
expressedThrough
chosen
Indicates that something (such as an idea, emotion, or content) is conveyed, manifested, or communicated by means of a particular medium, form, or channel.
-
C.
equivalentTo
Indicates that two entities represent the same concept, value, or state, and can be treated as interchangeable in the given context.
-
D.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
E.
isInterpretedBy
Indicates that something (such as data, a work, or a signal) is given meaning, understanding, or explanation by a particular agent or process.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a2605b372c8190831570aa6532cc96 |
completed | Feb. 28, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69a25b7a8d148190aacdcc8ccb35c7f3 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.