Triple
T10639789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Notopteridae |
E250690
|
entity |
| Predicate | finMovement |
P23546
|
FINISHED |
| Object | undulating anal fin |
—
|
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: undulating anal fin | Statement: [Notopteridae, finMovement, undulating anal fin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finMovement Context triple: [Notopteridae, finMovement, undulating anal fin]
-
A.
recordsMovementOf
chosen
Indicates that something captures or logs the movement or change in position of an entity over time.
-
B.
fundsFlowThrough
Indicates that financial resources are transferred or routed from one entity to another via an intermediate entity, account, or channel.
-
C.
flowsAcross
Indicates that one entity moves or extends in a continuous stream from one side of another entity to the other, traversing its area or boundary.
-
D.
transactionNature
Indicates the type or character of a transaction, specifying what kind of exchange or operation is taking place between the involved parties.
-
E.
capitalMoveTo
Indicates that the status of being a capital city is transferred from one location to another, marking a change in the official seat of government.
- 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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dfcbe5308190986bba438d19e852 |
completed | April 8, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69d6dd83b114819098e84dc658e82d7e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:04 p.m.