Triple
T31957712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Churchill class |
E815951
|
entity |
| Predicate | designEvolutionOf |
P2369
|
FINISHED |
| Object | Valiant class |
—
|
NE NERFINISHED |
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: Valiant class | Statement: [Churchill class, designEvolutionOf, Valiant class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designEvolutionOf Context triple: [Churchill class, designEvolutionOf, Valiant class]
-
A.
designEvolution
chosen
Indicates how the design of an entity changes, develops, or is refined over time or across versions.
-
B.
evolutionaryProcess
Indicates a relationship where one entity undergoes gradual genetic or trait changes over generations, driven by mechanisms like mutation, selection, and drift, resulting in evolutionary transformation.
-
C.
evolutionaryFeature
Indicates a characteristic or trait that has arisen or been shaped through evolutionary processes in an entity.
-
D.
evolutionaryDescription
Indicates how an entity has changed, adapted, or developed over time through evolutionary processes.
-
E.
evolutionControlledBy
Indicates that the process or course of evolution of an entity is directed, regulated, or determined by another entity.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
Created at: May 1, 2026, 12:08 a.m.