Triple
T12675580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kobe Science Museum |
E302801
|
entity |
| Predicate | hasExhibitsType |
P54449
|
FINISHED |
| Object | science |
—
|
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: science | Statement: [Kobe Science Museum, hasExhibitsType, science]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExhibitsType Context triple: [Kobe Science Museum, hasExhibitsType, science]
-
A.
hasExhibits
Indicates that an entity (such as a museum, gallery, or event) displays or presents certain items, artworks, or objects as part of its collection or show.
-
B.
hasExhibitsFrom
Indicates a relationship where one entity (typically a venue or collection) includes or displays exhibits originating from another entity (such as an artist, institution, or location).
-
C.
hasExhibitCategory
chosen
Indicates that an exhibit is associated with a particular category or type of exhibit.
-
D.
hasMainExhibitionType
Indicates that an entity is associated with a primary or predominant type of exhibition it presents or hosts.
-
E.
hasExhibitionsAbout
Indicates that one entity organizes or presents exhibitions whose subject matter concerns 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961b0d9c88190a05d6cbcb7a1642d |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:20 p.m.