Triple
T52407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yale University campus |
E1028
|
entity |
| Predicate | foundedWith |
P3263
|
FINISHED |
| Object | early Yale College buildings in New Haven |
—
|
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: early Yale College buildings in New Haven | Statement: [Yale University campus, foundedWith, early Yale College buildings in New Haven]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedWith Context triple: [Yale University campus, foundedWith, early Yale College buildings in New Haven]
-
A.
foundedFor
Indicates that an entity was established or created specifically to serve, support, or benefit another entity or purpose.
-
B.
foundedAs
Indicates the original name or form under which an organization, institution, or entity was first established.
-
C.
foundedOn
Indicates that an entity was established, created, or brought into existence on a specific date or point in time.
-
D.
foundedBefore
Indicates that one entity was established or created at an earlier time than the other entity.
-
E.
foundedAfter
Indicates that one entity was founded at a later time than 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24c709c248190bcd442c8d508e48c |
completed | Feb. 28, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69a24ac3c8dc819099849023bdaa35a9 |
completed | Feb. 28, 2026, 1:54 a.m. |
| PDg | Predicate description generation | batch_69a24c6ff0588190b0fd864da9aa8569 |
completed | Feb. 28, 2026, 2:01 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.