Triple
T15526916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Yellows |
E369106
|
entity |
| Predicate | denotesSuccess |
P119030
|
FINISHED |
| Object | one of Israel’s most successful football clubs |
—
|
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: one of Israel’s most successful football clubs | Statement: [The Yellows, denotesSuccess, one of Israel’s most successful football clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denotesSuccess Context triple: [The Yellows, denotesSuccess, one of Israel’s most successful football clubs]
-
A.
succeededUnder
Indicates that one entity achieved success or attained a position while operating under the authority, leadership, or conditions established by another entity.
-
B.
succeedsBy
Indicates that one entity comes after or replaces another in a sequence, order, or position.
-
C.
succeededByName
Indicates that one entity is followed or replaced by another entity identified by a specific name.
-
D.
isSuccessful
Indicates that an action, process, or attempt has achieved its intended goal or outcome.
-
E.
succeedsTo
Indicates that one entity takes over a role, position, or function previously held by another entity, following it in sequence or authority.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e04145178481909fb0339a79d4239e |
completed | April 16, 2026, 1:54 a.m. |
| PD | Predicate disambiguation | batch_69ded28ab0588190a47a9090d1238707 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57165288190979b7acb71ad5145 |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 4:05 a.m.