Triple
T18494415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John "Jack" Young |
E451902
|
entity |
| Predicate | likelyNotability |
P131883
|
FINISHED |
| Object | prominent local figure |
—
|
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: prominent local figure | Statement: [John "Jack" Young, likelyNotability, prominent local figure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyNotability Context triple: [John "Jack" Young, likelyNotability, prominent local figure]
-
A.
lacksNotabilityAs
Indicates that one entity is considered insufficiently notable or significant to be associated with or classified as the other entity.
-
B.
relativeNotability
Indicates how notable or prominent one entity is in comparison to another entity or set of entities.
-
C.
isNotable
Indicates that an entity is recognized as significant, prominent, or worthy of attention within a particular context or domain.
-
D.
hasNotabilityNote
Indicates that there is an associated note or annotation explaining the significance, prominence, or special relevance of the subject.
-
E.
notableLevel
Indicates the degree or extent to which something is considered notable or significant.
- 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e532bf206c8190a146cd1abd752152 |
completed | April 19, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2b93bc8190a6070018d7046547 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:35 a.m.