Triple
T16789124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nematomorpha |
E408056
|
entity |
| Predicate | knownFromContinents |
P106344
|
FINISHED |
| Object | worldwide except Antarctica |
—
|
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: worldwide except Antarctica | Statement: [Nematomorpha, knownFromContinents, worldwide except Antarctica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownFromContinents Context triple: [Nematomorpha, knownFromContinents, worldwide except Antarctica]
-
A.
recognizedAsContinentBy
Indicates that one entity is regarded or classified as a continent by another specified entity or authority.
-
B.
knownFrom
Indicates that one entity is aware of, has learned about, or recognizes another entity through a specified source, context, or medium.
-
C.
continentFound
chosen
Indicates that a specified continent is the location where a particular entity is found or occurs.
-
D.
continentType
Indicates that one entity is classified as a specific type or category of continent in relation to another entity.
-
E.
continentReference
Indicates that one entity serves as a reference or pointer to a specific continent associated with another entity.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2a50e18819090a30e1f38e520e0 |
completed | April 18, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.