Triple
T130717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zionism |
E2647
|
entity |
| Predicate | supportedByDocumentYear |
P4133
|
FINISHED |
| Object | 1917 |
—
|
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: 1917 | Statement: [Zionism, supportedByDocumentYear, 1917]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedByDocumentYear Context triple: [Zionism, supportedByDocumentYear, 1917]
-
A.
hasSupported
Indicates that one entity has provided assistance, endorsement, or backing to another entity, either materially, emotionally, or through advocacy.
-
B.
doesNotApplyRetroactivelyTo
Indicates that a rule, law, or condition does not affect events, actions, or situations that occurred before it came into effect.
-
C.
supportsClaim
chosen
Indicates that one entity provides evidence, reasoning, or backing that strengthens or validates the truth or credibility of another entity’s claim.
-
D.
supportsPolicy
Indicates that one entity endorses, backs, or is in favor of a particular policy or set of policies.
-
E.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
- 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_69a2520c0f3481908b0ed054a2fca8d0 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257845c548190bfb49409988d1c57 |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a2564da96c8190aa8204de25229c15 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.