Triple
T15559321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liga Leumit |
E370953
|
entity |
| Predicate | hasHistoricalNameStatus |
P28623
|
FINISHED |
| Object | former top division of Israel |
—
|
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: former top division of Israel | Statement: [Liga Leumit, hasHistoricalNameStatus, former top division of Israel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalNameStatus Context triple: [Liga Leumit, hasHistoricalNameStatus, former top division of Israel]
-
A.
hasHistoricNameVariant
Indicates that an entity has an alternative name that was used in a historical period or past context.
-
B.
historicalNameType
Indicates that the relationship specifies the type or category of a historical name associated with an entity.
-
C.
historicalStatusOf
chosen
Indicates the historical condition, role, or classification that an entity held during a specific past period or context.
-
D.
hasHistoricNickname
Indicates that an entity is known by a nickname that has historical significance or longstanding traditional use.
-
E.
regionHistoricalName
Indicates that a region has been known by a particular historical name during some past period.
- 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04dda3ab88190ab383333ce69fe8f |
completed | April 16, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69deda7e6e748190b29ccce23298afef |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:09 a.m.