Triple
T38068001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gallesia integrifolia |
E950521
|
entity |
| Predicate | nativeStatusInBrazil |
P155001
|
FINISHED |
| Object | native 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: native species | Statement: [Gallesia integrifolia, nativeStatusInBrazil, native species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nativeStatusInBrazil Context triple: [Gallesia integrifolia, nativeStatusInBrazil, native species]
-
A.
statusInBrazil
chosen
Indicates the legal, social, or operational status that an entity holds specifically within the context of Brazil.
-
B.
BrazilNeededResult
Indicates that Brazil required or depended on a particular outcome or result to occur or be achieved.
-
C.
roleInBrazil
Indicates that an entity holds or held a specific role, position, or function within the context of Brazil.
-
D.
mainAreaInBrazil
Indicates that a given area or region is the primary or most significant area located within Brazil for a specified entity or context.
-
E.
legalStatusInPortugal
Indicates the legal status or classification that an entity holds specifically within the jurisdiction of Portugal.
- 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc44c7e73c819082d4fc1900fb9632 |
completed | May 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69fbc8efffbc8190a139798ad1880526 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:21 p.m.