Triple
T31657041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lehigh Valley Zoo |
E807883
|
entity |
| Predicate | isRegionalZooFor |
P79172
|
FINISHED |
| Object | Lehigh Valley region |
—
|
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: Lehigh Valley region | Statement: [Lehigh Valley Zoo, isRegionalZooFor, Lehigh Valley region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRegionalZooFor Context triple: [Lehigh Valley Zoo, isRegionalZooFor, Lehigh Valley region]
-
A.
isMajorZooIn
Indicates that a zoo is a primary or significant zoological institution located within a specified geographic area or jurisdiction.
-
B.
hasZoo
Indicates that one entity possesses, operates, or is associated with a zoo.
-
C.
zooAlternativeName
Indicates that a zoo is known by an alternative or additional name.
-
D.
isRegionalMuseum
Indicates that a museum operates at a regional level, serving and representing a specific geographic area rather than a local, national, or international scope.
-
E.
zooLocation
chosen
Indicates that a zoo is located in or associated with a specific geographic place or administrative area.
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 10:55 p.m.