Triple
T25000273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yellow River Delta National Nature Reserve |
E625697
|
entity |
| Predicate | plantSpeciesRecorded |
P83264
|
FINISHED |
| Object | over 600 |
—
|
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 600 | Statement: [Yellow River Delta National Nature Reserve, plantSpeciesRecorded, over 600]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plantSpeciesRecorded Context triple: [Yellow River Delta National Nature Reserve, plantSpeciesRecorded, over 600]
-
A.
plantType
Indicates the specific kind or category of plant that an entity is classified as.
-
B.
notableTreeSpecies
Indicates that the subject place or area is known for, or characterized by, the specified tree species.
-
C.
associatedFlora
chosen
Indicates a relationship where specific plants or vegetation are characteristically linked to, occur with, or are commonly found in association with a given entity or environment.
-
D.
plantGenus
Indicates that one entity is a biological genus to which the plant entity belongs.
-
E.
hostsPlantOf
Indicates that one entity serves as a host environment or substrate on which a particular plant lives, grows, or depends.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44b0b35048190ae886a4fd5d385a7 |
completed | May 1, 2026, 6:41 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:04 a.m.