Triple
T9552546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ray Noble |
E230457
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Noble |
E521381
|
NE 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: Noble | Statement: [Ray Noble, familyName, Noble]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Noble Context triple: [Ray Noble, familyName, Noble]
-
A.
Noble
chosen
Noble is a surname of English origin historically associated with social rank and often borne by families of distinction.
-
B.
Regal
Regal is a major American movie theater chain known for operating multiplex cinemas across the United States.
-
C.
Worthy
Worthy is the surname of James Worthy, the Hall of Fame former Los Angeles Lakers basketball star known for his clutch playoff performances in the 1980s.
-
D.
Majesty
Majesty is a formal honorific style used to address or refer to a reigning monarch, typically a king or queen.
-
E.
The Most Noble
The Most Noble is an honorific style used in the United Kingdom for holders of the highest ranks of the peerage, such as dukes and certain great officers of state.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca847d3be8819099c9dad2a7e786f1 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd991f87e48190b5a5f4b3dfe7c1dd |
completed | April 1, 2026, 10:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d15286f7c881909258b9f06a81e464 |
completed | April 4, 2026, 6:03 p.m. |
Created at: March 30, 2026, 8:02 p.m.