Triple
T34672635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pom |
E890415
|
entity |
| Predicate | associatedWithFameOf |
P197651
|
FINISHED |
| Object | Pom Klementieff |
E256909
|
NE 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: Pom Klementieff | Statement: [Pom, associatedWithFameOf, Pom Klementieff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithFameOf Context triple: [Pom, associatedWithFameOf, Pom Klementieff]
-
A.
associatedWithFameAspect
Indicates that an entity is connected to or characterized by a particular aspect or dimension of fame.
-
B.
fameFor
Indicates that one entity is widely known or recognized specifically because of, or in connection with, another entity.
-
C.
hasFamousAssociationWith
chosen
Indicates a notable or widely recognized connection or relationship between two entities, often due to public attention, historical significance, or cultural impact.
-
D.
basedOnFameFrom
Indicates that something is determined, influenced, or derived from the level or source of fame associated with an entity.
-
E.
madeInternationallyFamousBy
Indicates that one entity became widely known across multiple countries as a result of the actions, influence, or association of another entity.
- F. None of above.
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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a375bd39cc48190af7fb7c8cd888c8f |
completed | June 21, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:05 a.m.