Triple
T4914475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olympus National Park |
E110313
|
entity |
| Predicate | hasFloraSpeciesCount |
P6211
|
FINISHED |
| Object | over 1700 plant species |
—
|
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: over 1700 plant species | Statement: [Olympus National Park, hasFloraSpeciesCount, over 1700 plant species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFloraSpeciesCount Context triple: [Olympus National Park, hasFloraSpeciesCount, over 1700 plant species]
-
A.
numberOfSpecies
chosen
Indicates the count of distinct species associated with a given entity or context.
-
B.
hasNativeSpecies
Indicates that a particular species naturally occurs and evolved in a specified geographic area or habitat, rather than being introduced from elsewhere.
-
C.
hasWildPopulationOf
Indicates that a location or area contains a naturally occurring, non-captive population of the specified species.
-
D.
numberOfPlants
Indicates the total count of plants associated with a given entity or context.
-
E.
hasEndemicSpecies
Indicates that a place or region contains species that are native to and found only within that specific geographic 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_69bd44132b94819088522d92beaadc78 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e9f12b48190b3cb5378958d03cd |
completed | March 20, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69bd6c325e188190823836d79934e9bc |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:29 p.m.