Triple
T3217452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galathea National Park |
E67429
|
entity |
| Predicate | hasFaunaType |
P16808
|
FINISHED |
| Object | marine fauna |
—
|
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: marine fauna | Statement: [Galathea National Park, hasFaunaType, marine fauna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFaunaType Context triple: [Galathea National Park, hasFaunaType, marine fauna]
-
A.
haveType
chosen
Indicates that an entity belongs to or is classified under a specified type or category.
-
B.
hasTypeGenus
Indicates that one entity is the type genus that formally defines or represents the taxonomic group of the other entity.
-
C.
hasPhylum
Indicates that an entity (typically a biological taxon or organism) is classified as belonging to a particular phylum in a taxonomic hierarchy.
-
D.
hasDuneType
Indicates that one entity is characterized by or associated with a specific type or classification of dune.
-
E.
hasFlagshipSpecies
Indicates that one entity (typically a site, region, or conservation program) is associated with or represented by a particular flagship species used to promote awareness or protection.
- 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_69ad858b8adc8190ad989712c87a476b |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adab0ae494819093d39c367facde27 |
completed | March 8, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0bb6c48190a0659c67d40ee37c |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:08 p.m.