Triple
T355753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Museum of Life and Science |
E7538
|
entity |
| Predicate | servesAudience |
P793
|
FINISHED |
| Object | families |
—
|
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: families | Statement: [Museum of Life and Science, servesAudience, families]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesAudience Context triple: [Museum of Life and Science, servesAudience, families]
-
A.
hasAudience
chosen
Indicates that an entity is intended to be received, viewed, or engaged with by a particular group of people.
-
B.
secondaryAudience
Indicates that an entity is a secondary or additional intended audience or target group for another entity (such as a work, message, or product), beyond the primary audience.
-
C.
approximateAudienceSize
Indicates an estimated number of individuals or entities that are expected to be reached or affected in a given context.
-
D.
audienceSizeApproximate
Indicates an estimated or approximate number of people in the audience for an event or content.
-
E.
sectorServed
Indicates the industry or economic sector that an entity primarily serves or targets with its activities, products, or services.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebad8bf08190b4a38ffd9157d641 |
completed | Feb. 28, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69a2e9589e7c8190b2d3af8f858c96af |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.