Triple
T25272077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antaresia maculosa |
E633592
|
entity |
| Predicate | hasBodyPattern |
P8151
|
FINISHED |
| Object | spotted |
—
|
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: spotted | Statement: [Antaresia maculosa, hasBodyPattern, spotted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBodyPattern Context triple: [Antaresia maculosa, hasBodyPattern, spotted]
-
A.
hasBodyOf
Indicates that one entity possesses, contains, or is composed of the physical body or main substance of another entity.
-
B.
haveBody
Indicates that one entity possesses, contains, or is associated with another entity as its body or main physical/content component.
-
C.
hasPattern
chosen
Indicates that one entity exhibits, follows, or is characterized by a specific recurring form, structure, or design defined by another entity.
-
D.
hasSupportBody
Indicates that one entity serves as a supporting structure or body for another entity.
-
E.
bodyPattern
Indicates a recurring or characteristic configuration, arrangement, or sequence exhibited by a body or physical form.
- 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_69e75a92f48881909974ff9c11150a2e |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48ba2bb608190bb26a5a496fff3b8 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 1:16 p.m.