Triple
T36281598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carapidae |
E892956
|
entity |
| Predicate | describedAsFamilyInYear |
P143666
|
FINISHED |
| Object | 1856 |
—
|
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: 1856 | Statement: [Carapidae, describedAsFamilyInYear, 1856]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describedAsFamilyInYear Context triple: [Carapidae, describedAsFamilyInYear, 1856]
-
A.
describedAsFamilyBy
Indicates that one entity is characterized or referred to as family by another entity.
-
B.
describedAsFamilyIn
Indicates that one entity is characterized or referred to as family in the context of another entity or setting.
-
C.
describedInFamily
Indicates that an entity is mentioned or characterized within a specific family-related context, such as a family record, lineage, or family description.
-
D.
familyIntroductionYear
chosen
Indicates the year in which a particular family (e.g., of products, organisms, or items) was first introduced, established, or formally recognized.
-
E.
identifiedAsFamilyIn
Indicates that one entity is recognized or designated as a family member within the context of a specified group, record, or setting.
- 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_69f76e4955c08190b8cfddca34fc0242 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
Created at: May 3, 2026, 4:09 p.m.