Triple
T23878055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golan-Globus Productions |
E600120
|
entity |
| Predicate | businessLeader |
P154304
|
FINISHED |
| Object | Yoram Globus |
—
|
NE NERFINISHED |
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: Yoram Globus | Statement: [Golan-Globus Productions, businessLeader, Yoram Globus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: businessLeader Context triple: [Golan-Globus Productions, businessLeader, Yoram Globus]
-
A.
businessBase
Indicates that one entity serves as the primary business foundation, core location, or main operational base for another entity.
-
B.
business
Indicates that an entity is engaged in commercial or professional activities, such as providing goods or services for profit.
-
C.
businessScale
Indicates the relative size or level of operations of a business, such as its scope, capacity, or market reach.
-
D.
businessTrait
Indicates that an entity possesses a particular business-related characteristic, quality, or attribute in relation to another entity or context.
-
E.
businessFunction
Indicates the specific role, activity, or operational function that an entity performs within a business context.
- 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_69e295318e148190b9979d8fc02e168f |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cc032c9c81909986ae6f672c1ad1 |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:23 p.m.