Triple
T10737159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamsin |
E253222
|
entity |
| Predicate | derivedFromMeaning |
P909
|
FINISHED |
| Object | twin |
—
|
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: twin | Statement: [Tamsin, derivedFromMeaning, twin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derivedFromMeaning Context triple: [Tamsin, derivedFromMeaning, twin]
-
A.
derivedFrom
chosen
Indicates that one entity originates, is obtained, or is developed from another source entity.
-
B.
semanticRootMeaning
Indicates the fundamental or core meaning that underlies a word, phrase, or expression in a semantic structure.
-
C.
evolvedMeaning
Indicates that the meaning or interpretation of something has changed or developed over time from its original sense.
-
D.
sourceLanguageMeaning
Indicates that one entity expresses the meaning or sense of another entity in a particular source language.
-
E.
literalMeaningApproximation
Indicates that one entity expresses an approximate or rough literal meaning of another entity, rather than an exact or fully precise interpretation.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d710410a04819090036597ac0d271c |
completed | April 9, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69d6f309a44881908e49e3ba478c35b4 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:14 p.m.