Triple
T35945470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crossosomataceae |
E1039575
|
entity |
| Predicate | belongsToAPGSystem |
P180432
|
FINISHED |
| Object | APG IV system |
—
|
NE NERFINISHED |
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: [Crossosomataceae, belongsToAPGSystem, APG IV system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToAPGSystem Context triple: [Crossosomataceae, belongsToAPGSystem, APG IV system]
-
A.
associatedSystem
Indicates that one entity is functionally or contextually linked to a particular system with which it interacts or to which it belongs.
-
B.
belongsToSystemType
Indicates that one entity is classified under, or is a member of, a particular system type.
-
C.
isPartOfAccessSystem
Indicates that something functions as a component or element within a larger access control or access management system.
-
D.
placedInAPGSystem
chosen
Indicates that an entity has been assigned or positioned within an APG (Angiosperm Phylogeny Group) classification system.
-
E.
hasParentSystem
Indicates that one system is hierarchically contained within or derived from another, which serves as its parent system.
- 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_69f76e24bbd0819096b837d35371639a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffc1550cb481908628e446d9b67f7b |
completed | May 9, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69ffc10a74708190ae90e2c378791f70 |
completed | May 9, 2026, 11:19 p.m. |
Created at: May 3, 2026, 4:07 p.m.