Triple
T34746952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyrillaceae |
E1001661
|
entity |
| Predicate | includedInAPGSystem |
P180432
|
FINISHED |
| Object | APG IV system |
E6168
|
NE 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: APG IV system | Statement: [Cyrillaceae, includedInAPGSystem, APG IV system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedInAPGSystem Context triple: [Cyrillaceae, includedInAPGSystem, APG IV system]
-
A.
placedInAPGSystem
chosen
Indicates that an entity has been assigned or positioned within an APG (Angiosperm Phylogeny Group) classification system.
-
B.
growsIn
Indicates that one entity develops, thrives, or increases in size or number within a specified environment, medium, or location.
-
C.
ortoBotanicoInstanceOf
Indicates that something is classified as an instance of an Orto Botanico (a specific botanical garden).
-
D.
isActinorhizalPlant
Indicates that a plant forms a symbiotic, nitrogen-fixing association with actinorhizal (Frankia) bacteria in its roots.
-
E.
isGrowingPartOf
Indicates that one entity is an expanding or developing component within the larger whole represented by another entity.
- F. None of above.
Provenance (4 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_69f76db0367081909b57c50a7fb03025 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a375bfb3c7c8190891623f4980e5b65 |
completed | June 21, 2026, 3:35 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.