Triple
T29417401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hydatellaceae |
E746061
|
entity |
| Predicate | previousPlacement |
P194418
|
FINISHED |
| Object | Monocots |
—
|
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: Monocots | Statement: [Hydatellaceae, previousPlacement, Monocots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousPlacement Context triple: [Hydatellaceae, previousPlacement, Monocots]
-
A.
previousLocationReplaced
Indicates that one location has been superseded or taken over by another location, replacing its previous role or position.
-
B.
placementIn
Indicates that one entity is located or positioned within the spatial or structural bounds of another entity.
-
C.
previousLocationName
Indicates that one entity specifies the name of a location where another entity was situated or occurred before its current location.
-
D.
previousAlignment
Indicates that one entity’s alignment or orientation occurred earlier in time than another’s.
-
E.
previousMeetingPlace
Indicates the location where two or more entities met on a prior occasion.
- F. None of above. chosen
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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
| PDg | Predicate description generation | batch_69fd6f9a8bd881909983fe8f4cd0ba98 |
completed | May 8, 2026, 5:07 a.m. |
Created at: April 28, 2026, 3:02 p.m.