Triple
T27504180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sternidae |
E694236
|
entity |
| Predicate | smallestMembers |
P64837
|
FINISHED |
| Object | small Sterna species |
—
|
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: small Sterna species | Statement: [Sternidae, smallestMembers, small Sterna species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: smallestMembers Context triple: [Sternidae, smallestMembers, small Sterna species]
-
A.
isSmallestOf
chosen
Indicates that an entity has the minimum size or value within a specified set or group of entities.
-
B.
smallestStandingType
Indicates that the subject is the smallest (in size, scale, or magnitude) entity among those that are currently standing or in an upright/active state.
-
C.
minimumNumberOfMembers
Indicates the smallest allowable or required number of members that must be present or involved in a given context or group.
-
D.
largestKnownMembers
Indicates that the related entities are the largest known members within a specified group, category, or set.
-
E.
largestMemberOf
Indicates that an entity is the member of a group or set that has the greatest size, extent, or magnitude according to a specified measure.
- 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_69ef538370888190b1ddf53bb4831188 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62ec57824819093909e9a5f04a592 |
completed | May 2, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 1:12 p.m.