Triple
T36174449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curie Hospital |
E1046541
|
entity |
| Predicate | hasNotableNamesakeOccupation |
P133817
|
FINISHED |
| Object | physicist |
—
|
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: physicist | Statement: [Curie Hospital, hasNotableNamesakeOccupation, physicist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableNamesakeOccupation Context triple: [Curie Hospital, hasNotableNamesakeOccupation, physicist]
-
A.
hasNotableNamesakeContribution
Indicates that an entity has made a significant contribution specifically related to or inspired by its notable namesake.
-
B.
notableNamesakeOccupation
chosen
Indicates that an entity is named after a notable person whose occupation or professional role is specified by the related value.
-
C.
hasFamousNamesake
Indicates that an entity shares its name with another well-known or notable entity.
-
D.
hasNotableNamesakeType
Indicates that an entity has a notable namesake of a specified type (such as a person, place, or work) that shares its name.
-
E.
hasNamesakeNotability
Indicates that one entity is notable or recognized specifically because it shares the same name as 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_69f76e3c1b10819081fc7a807a71cf84 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.