Triple
T37678713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birpai nation |
E938164
|
entity |
| Predicate | hasTraditionalCountryFeature |
P197770
|
FINISHED |
| Object | coastal plains |
—
|
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: coastal plains | Statement: [Birpai nation, hasTraditionalCountryFeature, coastal plains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalCountryFeature Context triple: [Birpai nation, hasTraditionalCountryFeature, coastal plains]
-
A.
hasTraditionalCountryNear
Indicates that one entity has a traditional or culturally recognized country located geographically close to it.
-
B.
hasTraditionalFeatures
Indicates that something possesses characteristics or attributes commonly associated with established traditions or customary practices.
-
C.
hasTraditionalTerritoryType
Indicates that an entity’s traditional territory is classified as belonging to a specific type or category of territory.
-
D.
isTraditionalInCountry
Indicates that something is customary, long-established, or commonly practiced within a particular country.
-
E.
hasTraditionalRegionType
chosen
Indicates that an entity is associated with or classified by a specific type of traditional region.
- 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_69f76ed7b1408190ba8c93c53cb8becf |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0048697bd081909073640666ca6a96 |
completed | May 10, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_6a0047bf3c248190a9ac97a7afdfe2cb |
completed | May 10, 2026, 8:54 a.m. |
Created at: May 3, 2026, 4:18 p.m.