Triple
T31623301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avocettina infans |
E806951
|
entity |
| Predicate | hasBilateralSymmetry |
P50368
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Avocettina infans, hasBilateralSymmetry, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBilateralSymmetry Context triple: [Avocettina infans, hasBilateralSymmetry, true]
-
A.
isBilateral
Indicates that the relationship or interaction involves two sides, parties, or entities mutually.
-
B.
symmetryOf
Indicates that one entity is the symmetry counterpart or symmetric form of another entity, typically related by a specific symmetry operation or transformation.
-
C.
hasAsymmetry
Indicates that one entity exhibits a lack of symmetry or an uneven, non-mirrored relationship or structure relative to another entity.
-
D.
bilaterallyPaired
Indicates that the relationship or structure involves two corresponding or matching parts on opposite sides of a central axis.
-
E.
isSymmetrical
chosen
Indicates that an object, pattern, or configuration remains unchanged or mirrored when transformed by a symmetry operation such as reflection, rotation, or inversion.
- 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_69f348d7883c8190b6c13ab92b7ef076 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 30, 2026, 10:42 p.m.