Triple
T33216893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plagiogyriaceae |
E850312
|
entity |
| Predicate | hasSporeProductionSite |
P194953
|
FINISHED |
| Object | sporangia |
—
|
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: sporangia | Statement: [Plagiogyriaceae, hasSporeProductionSite, sporangia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSporeProductionSite Context triple: [Plagiogyriaceae, hasSporeProductionSite, sporangia]
-
A.
sporeFormation
Indicates the process by which an organism produces and releases spores as a means of reproduction, survival, or dispersal.
-
B.
hasCultivationSite
Indicates that an entity possesses or is associated with a specific location where cultivation or growing activities take place.
-
C.
hasTeleomorph
Indicates a relationship where one organism or taxon has a corresponding sexual (teleomorphic) form in its life cycle or classification.
-
D.
sporeType
Indicates the specific kind or category of spores associated with an entity.
-
E.
hasSporophyteCharacteristic
Indicates that an entity possesses a characteristic or trait associated with the sporophyte stage of a life cycle.
- 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_69f3496083dc8190b229bb6932dc548b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
| PDg | Predicate description generation | batch_69fd91a44268819081b372296e3aa116 |
completed | May 8, 2026, 7:32 a.m. |
Created at: May 1, 2026, 1:30 a.m.