Triple
T2024575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbus Platform |
E44178
|
entity |
| Predicate | marksShiftToward |
P34686
|
FINISHED |
| Object | greater appreciation of Jewish peoplehood |
—
|
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: greater appreciation of Jewish peoplehood | Statement: [Columbus Platform, marksShiftToward, greater appreciation of Jewish peoplehood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marksShiftToward Context triple: [Columbus Platform, marksShiftToward, greater appreciation of Jewish peoplehood]
-
A.
marksStylisticShiftFrom
Indicates that one element signals a change in style, tone, or manner relative to another element.
-
B.
shiftedUnder
Indicates that one entity has been moved or displaced to a position beneath another entity.
-
C.
markType
Indicates the specific category or kind of mark associated with or applied to an entity.
-
D.
marks
Indicates that one entity makes a visible or symbolic sign on, or designates, another entity for identification, emphasis, or distinction.
-
E.
movementIn
Indicates a relationship where an entity moves within, into, or inside a specified area, space, or container.
- 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8f2cd5c8190b19da6f6aa2001d6 |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a656248190ac2ced196b35bc6b |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb85fe7a08190b991b1f23bc34f93 |
completed | March 7, 2026, 5:32 a.m. |
Created at: March 4, 2026, 7:38 p.m.