Triple
T22294583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polyphaga |
E551082
|
entity |
| Predicate | hasSuperfamiliesCount |
P31487
|
FINISHED |
| Object | more than 150 |
—
|
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: more than 150 | Statement: [Polyphaga, hasSuperfamiliesCount, more than 150]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuperfamiliesCount Context triple: [Polyphaga, hasSuperfamiliesCount, more than 150]
-
A.
hasRepresentativeFamily
Indicates that an entity is associated with a particular family that serves as its representative or characteristic example.
-
B.
numberOfFamilies
chosen
Indicates the total count of distinct family units associated with a given entity or context.
-
C.
isLargestSubfamilyOf
Indicates that one group or category is the largest subfamily within another, typically in terms of number of members or size.
-
D.
hasPhysicalFamily
Indicates that one entity is related to another as a member of the same biological or legally recognized family.
-
E.
hasNumberOfForfeda
Indicates a relationship where an entity is associated with a specific count of forfeda (additional Ogham letters).
- 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_69e11e45fb848190a1b2ae21296e3a5f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1560f06008190b58e71f7c1bd46f7 |
completed | April 29, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:41 p.m.