Triple
T1155311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ray Tomlinson |
E23769
|
entity |
| Predicate | usedSymbolInEmail |
P25371
|
FINISHED |
| Object | @ |
—
|
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: @ | Statement: [Ray Tomlinson, usedSymbolInEmail, @]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedSymbolInEmail Context triple: [Ray Tomlinson, usedSymbolInEmail, @]
-
A.
nameUsedIn
Indicates that a particular name is employed or referenced within a specified context, work, or usage setting.
-
B.
usedLabel
Indicates that one entity has applied, assigned, or referenced a particular label to another entity or resource.
-
C.
nameUsedBy
Indicates that a particular name is employed or referenced by a specific entity.
-
D.
usedPseudonym
Indicates that an entity performed an action or participated in a context under a name that was not their real or primary identity.
-
E.
nameUsedToAvoid
Indicates that one entity uses a particular name or designation in order to avoid another entity or an unwanted situation involving that entity.
- 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_69a493f0d32c8190ac74bad3c87f2641 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc912300819084c9c69783055a70 |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb50d19c81908a98dbbb04a8906f |
completed | March 1, 2026, 10:18 p.m. |
| PDg | Predicate description generation | batch_69a4bc47fce48190825d3a877251f789 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:44 p.m.