Triple
T23689201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bionectriaceae |
E585251
|
entity |
| Predicate | hasMembersWith |
P153407
|
FINISHED |
| Object | perithecial ascomata |
—
|
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: perithecial ascomata | Statement: [Bionectriaceae, hasMembersWith, perithecial ascomata]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMembersWith Context triple: [Bionectriaceae, hasMembersWith, perithecial ascomata]
-
A.
hasMembers
Indicates that a group, organization, or collection includes certain entities as its members.
-
B.
hasListOfMembers
Indicates that an entity is associated with a collection containing its members or constituents.
-
C.
hasMemberFrom
Indicates that a group, organization, or collection includes at least one member originating from or belonging to a specified source, place, or category.
-
D.
hasSiblingMembers
Indicates that two entities are members of a group or organization and are siblings to each other within that membership context.
-
E.
hasMemberFromEach
Indicates that a group or collection includes at least one member originating from each specified category, set, or subgroup.
- 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_69e249037ce0819088b149608e98f685 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b5c0a218819096c2d174b004c47d |
completed | April 29, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f157cc43a881909ed2d8b0a09b5d73 |
completed | April 29, 2026, 12:58 a.m. |
Created at: April 17, 2026, 6:52 p.m.