Triple
T18375282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urera baccifera |
E446296
|
entity |
| Predicate | fruitArrangement |
P46737
|
FINISHED |
| Object | clusters |
—
|
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: clusters | Statement: [Urera baccifera, fruitArrangement, clusters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fruitArrangement Context triple: [Urera baccifera, fruitArrangement, clusters]
-
A.
arrangement
Indicates a relationship where entities are organized, ordered, or positioned in a particular configuration or sequence relative to one another.
-
B.
arrangementType
chosen
Indicates the specific kind or category of arrangement that characterizes how the related entities are organized or structured in relation to each other.
-
C.
arrangementFeatures
Indicates that one entity specifies or characterizes the structural or compositional features of an arrangement involving another entity.
-
D.
arranges
Indicates that one entity organizes, coordinates, or puts in order some event, objects, or circumstances involving another entity.
-
E.
fruitAdheresTo
Indicates that a fruit is physically attached or sticks to another surface or object.
- 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51759353481908aa2de599fd2cf3b |
completed | April 19, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:45 a.m.