Triple
T36971095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mendes family |
E914569
|
entity |
| Predicate | hasPublicProminence |
P168950
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mendes family, hasPublicProminence, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicProminence Context triple: [Mendes family, hasPublicProminence, true]
-
A.
hasProminence
Indicates that one entity stands out in importance, visibility, or influence relative to others within a given context.
-
B.
hasPublicity
chosen
Indicates that an entity has received or is associated with public attention, promotion, or media exposure.
-
C.
wasProminent
Indicates that an entity held a position of significant importance, influence, or visibility within a particular context or period.
-
D.
hasPublicFigure
Indicates that an entity is associated with or characterized by a specific public figure, such as a celebrity, politician, or other widely recognized individual.
-
E.
gainedProminenceFor
Indicates that an entity became widely recognized or notable specifically because of another entity, action, or achievement.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:14 p.m.