Triple
T32306942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delphinidae |
E825395
|
entity |
| Predicate | typicalGroupStructure |
P81509
|
FINISHED |
| Object | pods |
—
|
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: pods | Statement: [Delphinidae, typicalGroupStructure, pods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGroupStructure Context triple: [Delphinidae, typicalGroupStructure, pods]
-
A.
typicalGroup
Indicates that the subject belongs to or represents a standard, characteristic, or commonly occurring group associated with the object.
-
B.
groupStructure
chosen
Indicates that multiple entities are organized together as a collective unit with some defined internal arrangement or hierarchy.
-
C.
hasGroupStructure
Indicates that the related entities together form an algebraic group under a specified operation, satisfying closure, associativity, identity, and invertibility.
-
D.
organizingStructure
Indicates that one entity serves as the framework or arrangement that orders, coordinates, or structures another entity or set of entities.
-
E.
workStructure
Indicates how work is organized, arranged, or structured within or between entities.
- 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_69f349115304819084ee91d345b6c8aa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:45 a.m.