Triple
T1633462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elephant Lands |
E35308
|
entity |
| Predicate | hasVisitorAmenity |
P5622
|
FINISHED |
| Object | viewing shelters |
—
|
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: viewing shelters | Statement: [Elephant Lands, hasVisitorAmenity, viewing shelters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVisitorAmenity Context triple: [Elephant Lands, hasVisitorAmenity, viewing shelters]
-
A.
hasBackstageFacilities
Indicates that a venue or location provides backstage areas and related facilities for performers or staff.
-
B.
hasAccommodation
Indicates that an entity provides, owns, or is associated with a place for someone to stay or live.
-
C.
amenityLevel
Indicates the degree or quality of facilities, services, or conveniences provided in relation to something.
-
D.
hasFacilities
Indicates that an entity possesses, provides, or is equipped with certain facilities or physical resources.
-
E.
amenity
chosen
Indicates that one entity provides a useful facility, service, or feature that enhances the convenience or comfort of 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_69a886036bc081909ff5de16dbe5e8ea |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a96083e7308190abbf025fe8e43abb |
completed | March 5, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69a907cac610819083cafd4396b6d66c |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.