Triple
T23449571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phylica revoluta |
E567737
|
entity |
| Predicate | hasLeafMorphology |
P17481
|
FINISHED |
| Object | revolute leaves |
—
|
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: revolute leaves | Statement: [Phylica revoluta, hasLeafMorphology, revolute leaves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeafMorphology Context triple: [Phylica revoluta, hasLeafMorphology, revolute leaves]
-
A.
hasLeaves
Indicates that an entity possesses leaves as part of its structure or form.
-
B.
typicalLeafCharacteristic
chosen
Indicates the usual or defining features of a leaf that characterize it under normal conditions.
-
C.
hasStomata
Indicates that an entity possesses stomata, meaning it has the microscopic pores or openings typically used for gas exchange.
-
D.
leafPresence
Indicates whether leaves are present on an entity (such as a plant or tree) during a given time or condition.
-
E.
leafNumberCharacteristic
Indicates a relationship where an entity is associated with a specific count or quantitative characteristic of its leaves.
- 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_69e2458b4c888190b1d7998f9862a558 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a64c1ee081908ba3adf5ce80d6a5 |
completed | April 29, 2026, 6:33 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:52 p.m.