Triple
T24639759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milton J. Rubenstein |
E609925
|
entity |
| Predicate | hasNameake |
P19396
|
FINISHED |
| Object | Milton J. Rubenstein Museum of Science and Technology |
—
|
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: Milton J. Rubenstein Museum of Science and Technology | Statement: [Milton J. Rubenstein, hasNameake, Milton J. Rubenstein Museum of Science and Technology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameake Context triple: [Milton J. Rubenstein, hasNameake, Milton J. Rubenstein Museum of Science and Technology]
-
A.
hasNameGivenTo
Indicates that one entity is the name that has been assigned or given to another entity.
-
B.
nameOf
Indicates that one entity is the name or designation of another entity.
-
C.
hasNaming
Indicates that one entity assigns, bears, or is associated with a specific name or designation provided by another entity.
-
D.
hasPeopleName
Indicates that an entity is associated with a specific person's name.
-
E.
namesakeStatus
chosen
Indicates that one entity serves as the namesake of another, or that two entities share a relationship based on having the same name.
- 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_69e2c4d28f848190ac38c400060e943d |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be064ff88190b5d9e5ec75a41242 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6d0ab708190b2e3b94dd20ca76b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:33 a.m.