Triple
T14654002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cosima Niehaus |
E344062
|
entity |
| Predicate | cloneLine |
P115222
|
FINISHED |
| Object | Leda clones |
—
|
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: Leda clones | Statement: [Cosima Niehaus, cloneLine, Leda clones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cloneLine Context triple: [Cosima Niehaus, cloneLine, Leda clones]
-
A.
branchLine
Indicates a relationship where one line, route, or path diverges from and is subordinate to a main or primary line.
-
B.
subLine
Indicates that one line is a subordinate or component segment of another, typically representing a part–whole or hierarchical relationship between lines.
-
C.
builtLine
Indicates that an entity constructed or established a particular line, such as a route, boundary, or infrastructure segment.
-
D.
originalLine
Indicates that one entity is the initial or source version of a line from which other versions or derivatives may originate.
-
E.
connectedLine
Indicates that two entities are joined by a continuous line or linear connection.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb518f7dc8190877997ea4cd3eed2 |
completed | April 14, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:27 a.m.