Triple
T13689992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carme group |
E328234
|
entity |
| Predicate | hasCollisionalFamilyStatus |
P4276
|
FINISHED |
| Object | probable collisional family |
—
|
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: probable collisional family | Statement: [Carme group, hasCollisionalFamilyStatus, probable collisional family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollisionalFamilyStatus Context triple: [Carme group, hasCollisionalFamilyStatus, probable collisional family]
-
A.
belongsToFamily
chosen
Indicates that an entity is a member of, or is associated as part of, a specific family group.
-
B.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
C.
containsFamily
Indicates that one entity includes or encompasses members of a particular family group within it.
-
D.
hasFamilyRelationContext
Indicates that there exists a family-based relationship or kinship context connecting the referenced entities.
-
E.
hasRepresentativeFamily
Indicates that an entity is associated with a particular family that serves as its representative or characteristic example.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc6721c248190ac48491b5f39c8f0 |
completed | April 12, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:53 p.m.