Triple
T33543731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Angeles Southwest College |
E859143
|
entity |
| Predicate | transferDestinationType |
P198793
|
FINISHED |
| Object | four-year universities |
—
|
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: four-year universities | Statement: [Los Angeles Southwest College, transferDestinationType, four-year universities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferDestinationType Context triple: [Los Angeles Southwest College, transferDestinationType, four-year universities]
-
A.
transferDestination
Indicates the entity that serves as the receiving end or target location of a transfer from another entity.
-
B.
transferType
Indicates the specific method or category of how something is transferred from one entity to another.
-
C.
transferMode
Indicates the method or mechanism by which something is transferred from one entity to another.
-
D.
transferPartnerType
Indicates the role or category of the counterparty involved in a transfer relationship or transaction.
-
E.
sampleDestination
Indicates that something serves as, or is designated to be, the target location or endpoint for a sample.
- 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff069ec1348190815375c5c9e38404 |
completed | May 9, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69ff05ba57f88190a45d20f18044e0fb |
completed | May 9, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69ff069ddf948190bdfe438953249dd0 |
completed | May 9, 2026, 10:04 a.m. |
Created at: May 1, 2026, 1:39 a.m.