Triple
T4330625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manouria tortoises |
E96738
|
entity |
| Predicate | evolutionaryDescription |
P55597
|
FINISHED |
| Object | primitive tortoises |
—
|
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: primitive tortoises | Statement: [Manouria tortoises, evolutionaryDescription, primitive tortoises]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evolutionaryDescription Context triple: [Manouria tortoises, evolutionaryDescription, primitive tortoises]
-
A.
evolutionaryPhase
Indicates the stage or period an entity is in within a broader process of gradual development or evolution.
-
B.
stanceOnEvolution
Indicates the position, attitude, or viewpoint an entity holds regarding the concept, validity, or teaching of biological evolution.
-
C.
evolvedMeaning
Indicates that the meaning or interpretation of something has changed or developed over time from its original sense.
-
D.
evolvedIn
Indicates that an entity originated or developed within a specified environment, context, or location over evolutionary time.
-
E.
designEvolution
Indicates how the design of an entity changes, develops, or is refined over time or across versions.
- F. None of above. chosen
Provenance (4 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_69b34542fd908190b11b08faad8decfd |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3514c39748190900e13e70ed8848c |
completed | March 12, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69b34f4e13fc8190a42c519f37959d27 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff654308190b9717526120d80d3 |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:13 p.m.