Triple
T31794324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common Intellectual Experience core curriculum |
E811551
|
entity |
| Predicate | locationOfProvider |
P27029
|
FINISHED |
| Object | Collegeville, Pennsylvania |
E406011
|
NE 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: Collegeville, Pennsylvania | Statement: [Common Intellectual Experience core curriculum, locationOfProvider, Collegeville, Pennsylvania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfProvider Context triple: [Common Intellectual Experience core curriculum, locationOfProvider, Collegeville, Pennsylvania]
-
A.
platformLocation
Indicates the spatial position or placement of a platform relative to a reference point or environment.
-
B.
locationOfFacility
chosen
Indicates that a facility is situated at or associated with a specific geographic location.
-
C.
operationLocation
Indicates the place or site where an operation, activity, or process is carried out.
-
D.
propertyLocation
Indicates the geographical place or address where a property is situated or found.
-
E.
connectionLocation
Indicates the place or spatial context where a connection between entities occurs or is established.
- F. None of above.
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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a01c21d8bc481909dd9f5a6b89c0a92 |
completed | May 11, 2026, 11:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2eddc7448881908ff7cb67e64f0b11 |
completed | June 14, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_6a01bff5d1508190895e5bd2c04932b0 |
completed | May 11, 2026, 11:39 a.m. |
Created at: April 30, 2026, 11:40 p.m.