Triple
T12516695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sdiff |
E299206
|
entity |
| Predicate | changeMarker |
P99152
|
FINISHED |
| Object | "|" for differing lines |
—
|
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: "|" for differing lines | Statement: [sdiff, changeMarker, "|" for differing lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changeMarker Context triple: [sdiff, changeMarker, "|" for differing lines]
-
A.
changedFrom
Indicates that an entity previously had one state, value, or form and was altered or updated from that prior condition to a new one.
-
B.
marksShiftToward
Indicates a change or transition from one state, condition, or position toward another, highlighting the direction or trend of that shift.
-
C.
changeReason
Indicates the reason or justification for a modification or change made to an entity or its state.
-
D.
markingFeature
chosen
Indicates a feature that serves as a distinguishing mark or identifier associated with an entity.
-
E.
changesProperty
Indicates that one entity causes a change in a specific property or attribute of another entity.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d954b867dc8190af8a70f797e4d133 |
completed | April 10, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_69d954096af88190b6be81b008c82139 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.