Triple
T31068913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pál Lukács |
E791757
|
entity |
| Predicate | achievedInternationalFameIn |
P112499
|
FINISHED |
| Object | film |
—
|
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: film | Statement: [Pál Lukács, achievedInternationalFameIn, film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: achievedInternationalFameIn Context triple: [Pál Lukács, achievedInternationalFameIn, film]
-
A.
madeInternationallyFamousBy
Indicates that one entity became widely known across multiple countries as a result of the actions, influence, or association of another entity.
-
B.
fameFor
Indicates that one entity is widely known or recognized specifically because of, or in connection with, another entity.
-
C.
starMadeFamous
chosen
Indicates that one entity (such as a work, event, or role) is what caused another entity (typically a person) to become widely known or famous.
-
D.
famousAt
Indicates that an entity is widely known or recognized in a particular place, context, or time.
-
E.
isMoreFamousThan
Indicates that one entity is better known or more widely recognized by people than another entity.
- 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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:01 p.m.