Triple
T428210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Ball Zoo |
E9655
|
entity |
| Predicate | typicalVisitorProfile |
P10804
|
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: [John Ball Zoo, typicalVisitorProfile, families]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalVisitorProfile Context triple: [John Ball Zoo, typicalVisitorProfile, families]
-
A.
typicalAudience
chosen
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
B.
customerType
Indicates the classification or category assigned to a customer based on their characteristics, status, or relationship with a business.
-
C.
participantType
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
D.
typicalMembers
Indicates that the related entities are representative or characteristic members of a larger group, category, or class.
-
E.
typicalSpeaker
Indicates that the subject is a prototypical or characteristic speaker or source of utterances in the context of the object.
- 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_69a2e801e1d48190b505d1dd336b52ac |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eeecb64c81908c5c83ef7c0181e6 |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd7a3608190b8785c7b7205f6c1 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.