Triple
T32306792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prye |
E825391
|
entity |
| Predicate | historicalCultureNearby |
P92363
|
FINISHED |
| Object | Pyu civilization |
—
|
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: Pyu civilization | Statement: [Prye, historicalCultureNearby, Pyu civilization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalCultureNearby Context triple: [Prye, historicalCultureNearby, Pyu civilization]
-
A.
nearbyHeritageDestinations
Indicates that one or more heritage destinations are located close to a given reference point or entity in geographic space.
-
B.
heritageOfLocation
Indicates that a particular location possesses or is associated with a recognized cultural, historical, or natural heritage.
-
C.
nearbyArchaeologicalCulture
chosen
Indicates that one archaeological culture is geographically close to another archaeological culture.
-
D.
nearCulturalInstitution
Indicates that one entity is located close to, or in the immediate vicinity of, a cultural institution such as a museum, theater, gallery, or similar venue.
-
E.
nearbyHistoricalServiceFor
Indicates that a historical service or facility is located close to a given reference entity or location.
- 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_69f349115304819084ee91d345b6c8aa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff90b673248190b4dda9e005642d17 |
completed | May 9, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69ff8d5bee1081909274052945e98a6f |
completed | May 9, 2026, 7:39 p.m. |
Created at: May 1, 2026, 12:45 a.m.