Triple
T364461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jobs |
E7927
|
entity |
| Predicate | onWikipedia |
P7959
|
FINISHED |
| Object | https://en.wikipedia.org/wiki/Jobs_(surname) |
—
|
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: https://en.wikipedia.org/wiki/Jobs_(surname) | Statement: [Jobs, onWikipedia, https://en.wikipedia.org/wiki/Jobs_(surname)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onWikipedia Context triple: [Jobs, onWikipedia, https://en.wikipedia.org/wiki/Jobs_(surname)]
-
A.
hasOnlineEncyclopediaEntry
chosen
Indicates that an entity has a corresponding entry or article in an online encyclopedia.
-
B.
notedIn
Indicates that information about one entity is mentioned, recorded, or referenced within another entity, such as a document, record, or source.
-
C.
popularizedIn
Indicates that something became widely known, accepted, or fashionable within a particular place, time period, or context.
-
D.
notableExplorer
Indicates that the subject is recognized for significant achievements or prominence in the field of exploration.
-
E.
popularizedBy
Indicates that something became widely known, accepted, or fashionable as a result of the influence or actions of a particular agent.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebe6c1b4819083335e880c205ed6 |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95dbb208190b277fc5352a4ee84 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.