Triple
T672643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | School of Social Work |
E13005
|
entity |
| Predicate | hasValue |
P18302
|
FINISHED |
| Object | social responsibility |
—
|
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: social responsibility | Statement: [School of Social Work, hasValue, social responsibility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasValue Context triple: [School of Social Work, hasValue, social responsibility]
-
A.
hasCoreValue
Indicates that an entity possesses or is characterized by a fundamental guiding principle or core belief.
-
B.
hasCommonValue
Indicates that two or more entities share at least one identical value or attribute in common.
-
C.
hasMinimumValue
Indicates that an entity possesses a value that is the lowest permissible or observed within a specified set, range, or context.
-
D.
hasApproximateValue
Indicates that one entity’s value is close to, but not exactly equal to, the value of another entity within an acceptable margin of error.
-
E.
hasExactValue
Indicates that an entity possesses a specific, precisely defined value that must match exactly, without any deviation or tolerance.
- 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_69a4933d3bf88190972041cd8cf143b9 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a1b3682c8190a9b9a454480c3446 |
completed | March 1, 2026, 8:29 p.m. |
| PD | Predicate disambiguation | batch_69a49d1a16c48190af89e3b078a4957e |
completed | March 1, 2026, 8:10 p.m. |
| PDg | Predicate description generation | batch_69a4a1b240648190bf15415205399d97 |
completed | March 1, 2026, 8:29 p.m. |
Created at: March 1, 2026, 7:36 p.m.