Triple
T353781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swarthmore College |
E7499
|
entity |
| Predicate | hasCoreValue |
P12172
|
FINISHED |
| Object | social justice |
—
|
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 justice | Statement: [Swarthmore College, hasCoreValue, social justice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreValue Context triple: [Swarthmore College, hasCoreValue, social justice]
-
A.
hasCommonValue
Indicates that two or more entities share at least one identical value or attribute in common.
-
B.
isNucleusOf
Indicates that one entity functions as the central or most important core component of another entity.
-
C.
hasCODATAValue
Indicates that an entity is associated with a value specified or standardized by CODATA (Committee on Data for Science and Technology).
-
D.
hasCP
Indicates that an entity possesses, is associated with, or is characterized by a specific CP (such as a control point, contact person, or configuration parameter), depending on the domain context.
-
E.
hasPrimaryFunction
Indicates that one entity serves as the main or principal function or role of another entity.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eb80f524819093f4c2c18c3d615f |
completed | Feb. 28, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69a2e9571bd88190b6fcb16f21604720 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea0a4c448190a8a179daa9b90645 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.