Triple
T34681918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salesian Family |
E890643
|
entity |
| Predicate | hasSpecialConcernFor |
P150527
|
FINISHED |
| Object | poor young people |
—
|
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: poor young people | Statement: [Salesian Family, hasSpecialConcernFor, poor young people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpecialConcernFor Context triple: [Salesian Family, hasSpecialConcernFor, poor young people]
-
A.
subjectOfConcernFor
chosen
Indicates that one entity is regarded as a matter of worry, interest, or attention for another entity.
-
B.
hasHealthConcern
Indicates that an entity has a specific health-related issue, condition, or concern associated with it.
-
C.
hasManagementConcern
Indicates that one entity has responsibility, authority, or involvement in overseeing, directing, or managing another entity or activity.
-
D.
concernsSet
Indicates that something is about, relates to, or involves a particular set as its primary subject or focus.
-
E.
raisedConcernAbout
Indicates that one entity has expressed worry, doubt, or objection regarding another entity or issue.
- 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
Created at: May 1, 2026, 2:05 a.m.