Triple
T31982661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R.J. |
E816626
|
entity |
| Predicate | hasCanonicalNameSpelling |
P19207
|
FINISHED |
| Object | "R.J." with periods |
—
|
NE NERFINISHED |
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: "R.J." with periods | Statement: [R.J., hasCanonicalNameSpelling, "R.J." with periods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanonicalNameSpelling Context triple: [R.J., hasCanonicalNameSpelling, "R.J." with periods]
-
A.
hasCanonicalNameForm
chosen
Indicates that an entity is associated with its standard or officially recognized name form.
-
B.
hasCanonicalTerm
Indicates that one term in a set is designated as the standard or authoritative form used to represent a concept or entity.
-
C.
isCanonical
Indicates that something represents the standard, authoritative, or officially accepted form within a given context or system.
-
D.
hasCanonicalCharacter
Indicates that something is associated with or defined by its standard, officially recognized character representation.
-
E.
hasCanonicalRepresentation
Indicates that one entity is the standard or authoritative form in which another entity is represented.
- 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feb8e856d48190aa34ad8ee8376e1c |
completed | May 9, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_69feb82a2b6c8190a473cc25976897be |
completed | May 9, 2026, 4:29 a.m. |
Created at: May 1, 2026, 12:12 a.m.