Triple
T35367114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFUMS |
E1021660
|
entity |
| Predicate | fieldOfNamedPerson |
P184050
|
FINISHED |
| Object | X-ray crystallography |
—
|
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: X-ray crystallography | Statement: [RFUMS, fieldOfNamedPerson, X-ray crystallography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldOfNamedPerson Context triple: [RFUMS, fieldOfNamedPerson, X-ray crystallography]
-
A.
namedPersonField
Indicates that a particular data field is designated to contain a person’s name.
-
B.
famousIndividual
Indicates that an individual is widely known and recognized by a large number of people, typically for notable achievements, status, or public visibility.
-
C.
namedPersonNotableFor
Indicates that a person is especially known or recognized for a particular work, role, achievement, or characteristic.
-
D.
namedPersonOccupation
Indicates that a person is explicitly identified as having a particular occupation or job role.
-
E.
namedForNotablePersonFrom
Indicates that one entity is named in honor of a notable person who originates from another specified place or group.
- 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_69f76df000488190ab7c97f565677055 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.