Triple
T31552784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swainson, 1839 |
E805048
|
entity |
| Predicate | authorityForFamily |
P192500
|
FINISHED |
| Object | Cobitidae |
—
|
NE NERFINISHED |
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: Cobitidae | Statement: [Swainson, 1839, authorityForFamily, Cobitidae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorityForFamily Context triple: [Swainson, 1839, authorityForFamily, Cobitidae]
-
A.
allowsForFamily
Indicates that one entity enables or makes it possible for another entity to support or include family-related participation, benefits, or involvement.
-
B.
familyAuthority
Indicates that one entity holds recognized decision-making power or control over another within a family or household context.
-
C.
ownerFamily
Indicates that a family has ownership or proprietary rights over a particular entity or resource.
-
D.
familyRule
Indicates a rule, norm, or guideline that governs relationships or behavior within a family context.
-
E.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
- 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69fd0d0aebac8190868a7714ddb4f1fd |
completed | May 7, 2026, 10:07 p.m. |
Created at: April 30, 2026, 10:11 p.m.