Triple
T1507887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five College Consortium |
E33943
|
entity |
| Predicate | shares |
P16175
|
FINISHED |
| Object | courses |
—
|
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: courses | Statement: [Five College Consortium, shares, courses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shares Context triple: [Five College Consortium, shares, courses]
-
A.
share
chosen
Indicates that one entity gives, divides, or jointly uses a resource, item, or information with another entity.
-
B.
sharesIn
Indicates that one entity holds or possesses shares or ownership stakes in another entity.
-
C.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
D.
sharesFeatureWith
Indicates that two entities have at least one common attribute, property, or characteristic in common.
-
E.
sharesHead
Indicates that two entities have the same head element, leader, or top-level component in common.
- 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_69a885f352a4819099b24ff15489dede |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a8e2dd93dc8190a78443900e8d5564 |
completed | March 5, 2026, 1:56 a.m. |
| PD | Predicate disambiguation | batch_69a88728c150819095cdcdbfcabf4249 |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:24 p.m.