Triple
T15684872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mammoth (Amherst College mascot) |
E380170
|
entity |
| Predicate | representsValues |
P72867
|
FINISHED |
| Object | inclusivity |
—
|
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: inclusivity | Statement: [Mammoth (Amherst College mascot), representsValues, inclusivity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsValues Context triple: [Mammoth (Amherst College mascot), representsValues, inclusivity]
-
A.
representsAs
chosen
Indicates that one entity serves as a depiction, symbol, or stand-in for another entity in some representational context.
-
B.
areRepresentedBy
Indicates that one entity serves as a representation, proxy, or stand-in for another entity.
-
C.
representationIn
Indicates that one entity serves as a depiction, model, or stand-in for another entity within a given context or medium.
-
D.
representsInRelationsWith
Indicates that an entity serves as a representative or proxy for another entity within a specified relationship or set of relationships.
-
E.
representsThroughMembers
Indicates that an entity exercises representation or acts on behalf of another entity via its members rather than directly.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04f4b73d881908ec0f21393a01969 |
completed | April 16, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69deda8c856c8190882330114f9a1a5f |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:44 a.m.