Triple
T13694266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stomp the Yard |
E328343
|
entity |
| Predicate | setAt |
P24794
|
FINISHED |
| Object | historically Black university |
—
|
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: historically Black university | Statement: [Stomp the Yard, setAt, historically Black university]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setAt Context triple: [Stomp the Yard, setAt, historically Black university]
-
A.
setRecordAt
Indicates assigning or updating a record at a specific position or location within a collection or data structure.
-
B.
setWith
Indicates that one entity is grouped, combined, or associated together in a set or collection with another entity.
-
C.
setInto
Indicates placing or inserting one entity into another entity or context, often initiating a new state or condition.
-
D.
setLocation
chosen
Indicates assigning or updating the place or position where an entity is located.
-
E.
setsReferenceValue
Indicates that one entity assigns or establishes a reference value to be used as a standard or baseline for another entity or process.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc8757b648190a26181efbad09a43 |
completed | April 12, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:54 p.m.