Triple
T18968383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | difference principle |
E464100
|
entity |
| Predicate | evaluatedFrom |
P91138
|
FINISHED |
| Object | original position |
—
|
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: original position | Statement: [difference principle, evaluatedFrom, original position]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evaluatedFrom Context triple: [difference principle, evaluatedFrom, original position]
-
A.
evaluatedInContext
chosen
Indicates that an entity (such as a statement, result, or behavior) is assessed or interpreted within a specific contextual setting or framework.
-
B.
declaredFrom
Indicates that one entity is formally announced, stated, or proclaimed by another as its source or origin.
-
C.
evaluatesAs
Indicates that one entity is judged, interpreted, or assessed as having a particular value, role, or classification in relation to another.
-
D.
triggeredFrom
Indicates that one event, action, or process was initiated or caused as a result of another specific event, action, or process.
-
E.
measuredFrom
Indicates that a measurement or value is determined relative to, or using, a specified reference point or source.
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6172888819090a8b3cb1db20496 |
completed | April 20, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon