Triple
T35946492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fabid clade |
E1039596
|
entity |
| Predicate | hasMemberOrderCountApprox |
P20367
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [Fabid clade, hasMemberOrderCountApprox, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemberOrderCountApprox Context triple: [Fabid clade, hasMemberOrderCountApprox, 10]
-
A.
hasApproximateMemberCount
chosen
Indicates that an entity is associated with a group or collection for which only an estimated or non-exact number of members is known.
-
B.
hasApproximateOrderNumber
Indicates that an entity is associated with a non-exact, estimated, or approximate order number in a sequence or ordering.
-
C.
hasMemberOrders
Indicates that a group, organization, or collection has associated orders placed or held by its members.
-
D.
hasMemberCountType
Indicates the type or classification used to describe how the number of members in a group or collection is represented.
-
E.
hasApproximateStoreCount
Indicates that an entity is associated with an estimated or approximate number of stores, rather than an exact count.
- 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_69ff46afe7e481908f2862ed11c88db2 |
completed | May 9, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69ff45e9151881909c444a655e852165 |
completed | May 9, 2026, 2:34 p.m. |
Created at: May 3, 2026, 4:07 p.m.