Triple
T10672267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1762 Russell |
E251517
|
entity |
| Predicate | namedForFieldOfWork |
P83605
|
FINISHED |
| Object | astronomy |
—
|
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: astronomy | Statement: [1762 Russell, namedForFieldOfWork, astronomy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedForFieldOfWork Context triple: [1762 Russell, namedForFieldOfWork, astronomy]
-
A.
namedForWork
Indicates that one entity is named in honor of, or derived from the title of, a particular work (such as a book, film, artwork, or other creative production).
-
B.
fieldOfWork
Indicates the professional or academic domain in which an entity is primarily engaged or specializes.
-
C.
namedForWorkOn
chosen
Indicates that an entity is named in honor of another entity specifically because of that entity’s work or contributions in a particular field or endeavor.
-
D.
relatedWorkField
Indicates that one work is associated with or pertains to the same or a relevant field, discipline, or area of activity as another work.
-
E.
fieldOfSignificance
Indicates that something holds particular importance, relevance, or impact within a specified domain, context, or area of interest.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6f8659d40819087a2709bd24261ee |
completed | April 9, 2026, 12:52 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8a93208190a573061387e2aebb |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:09 p.m.