Triple
T32703698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trischen |
E836211
|
entity |
| Predicate | hasSeasonalWarden |
P31687
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Trischen, hasSeasonalWarden, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeasonalWarden Context triple: [Trischen, hasSeasonalWarden, yes]
-
A.
hasWarden
chosen
Indicates that one entity serves as the warden or supervisory authority responsible for another entity.
-
B.
hasSeasonalSpecies
Indicates that certain species are present or occur only during specific seasons in relation to a given context or location.
-
C.
hasSeasonalObjective
Indicates that an entity is associated with a specific objective or goal that is only relevant or active during a particular season or time period.
-
D.
hasSeasonalNature
Indicates that something exhibits characteristics, behavior, or occurrence patterns that vary according to specific seasons or times of the year.
-
E.
hasHuntingSeason
Indicates that there is a defined time period during which hunting of the referenced entity is legally permitted.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff6074bcd4819090b72cd6209ff206 |
completed | May 9, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69ff600aba888190812a6e7eca0283b8 |
completed | May 9, 2026, 4:25 p.m. |
Created at: May 1, 2026, 1:10 a.m.